Webinar - How Companies Use Couchbase: Common Use Cases

3,345 views

Published on

Couchbase Server serves an array of data-driven and performance-driven use cases such as social gaming, mobile apps, ad targeting, session store, and high availability caching. We will explore in-depth the most common use cases and share customer examples for each one.

Published in: Technology, Education
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,345
On SlideShare
0
From Embeds
0
Number of Embeds
1,576
Actions
Shares
0
Downloads
0
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide
  • Good Morning everyone
  • Webinar - How Companies Use Couchbase: Common Use Cases

    1. 1. How Companies useNoSQL and CouchbaseDon PintoProduct Marketing Manager
    2. 2. Couchbase ServerNoSQL Document Database
    3. 3. EasyScalabilityConsistent HighPerformanceAlwaysOn24x365Grow cluster withoutapplication changes, withoutdowntime with a single clickConsistent sub-millisecondread and write response timeswith consistent high throughputNo downtime for softwareupgrades, hardwaremaintenance, etc.JSONJSONJSONJSONJSONFlexible DataModelJSON document model withno fixed schema.Couchbase Server
    4. 4. NoSQL + Big DataMap-reduce againsthuge datasets to analyzeand find insights andanswersOperational database forweb and mobile apps withhigh performance at scalehttp://www.couchbase.com/develop/connectors/hadoop
    5. 5. Features in Couchbase Server 2.0JSON support Indexing and QueryingCross data center replicationIncremental Map ReduceJSONJSONJSONJSONJSON
    6. 6. Additional FeaturesBuilt-in clustering – All nodes equalData replication with auto-failoverZero-downtime maintenanceBuilt-in managed cachedAppend-only storage layerOnline compactionMonitoring and admin API & UISDK for a variety of languages
    7. 7. Common Use CasesSocial Gaming• Couchbase storesplayer and gamedata• Example customersinclude: Tencent• Tapjoy, UbisoftMobile Apps• Couchbase stores userinfo and app content• Example customersinclude: Kobo, PlaytikaAd Targeting• Couchbase storesuser information forfast access• Example customersinclude:AOL, Mediamind, ConvertroSession store• Couchbase Server as a key-value store• Example customers include:Concur, SabreUser Profile Store• Couchbase Server as akey-value store• Example customersinclude: TunewikiHigh availability cache• Couchbase Server used as a cache tier replacement• Example customers include: OrbitzContent & MetadataStore• Couchbase document storewith Elasticsearch• Example customersinclude: McGraw Hill3rd party data aggregation• Couchbase stores social media anddata feeds• Example customers include:Sambacloud
    8. 8. Common Use CasesSocial Gaming• Couchbase storesplayer and gamedata• Example customersinclude: Zynga• Tapjoy, Ubisoft, TencentMobile Apps• Couchbase stores userinfo and app content• Example customersinclude: Kobo, PlaytikaAd Targeting• Couchbase storesuser information forfast access• Example customersinclude:AOL, Mediamind, ConvertroSession store• Couchbase Server as a key-value store• Example customers include:Concur, SabreUser Profile Store• Couchbase Server as akey-value store• Example customersinclude: TunewikiHigh availability cache• Couchbase Server used as a cache tier replacement• Example customers include: OrbitzContent & MetadataStore• Couchbase document storewith Elasticsearch• Example customersinclude: McGraw Hill3rd party data aggregation• Couchbase stores social media anddata feeds• Example customers include:Sambacloud
    9. 9. • Content metadata• Content: Articles, text• Landing pages for website• Digital content:eBooks, magazine, researchmaterialContent and Metadata StoreUse Case: Content and Metadata Store• Flexibility to store any kind ofcontent• Fast access to content metadata(most accessed objects) andcontent• Full-text Search across data set• Scales horizontally as more contentgets added to the system• Fast access to metadata and content via object-managed cache• JSON provides schema flexibility to store all types of content andmetadata• Indexing and querying provides real-time analytics capabilitiesacross dataset• Integration with Elasticsearch for full-text search• Ease of scalability ensures that the data cluster can be grownseamlessly as the amount of user and ad data growsTypes of Data Application RequirementsWhy NoSQL and Couchbase
    10. 10. McGraw Hill Education LabsLearning portal
    11. 11. Use Case: Content and metadata storeBuilding a self-adapting, interactive learningportal with Couchbase
    12. 12. As learning move online in great numbersGrowing need to build interactive learning environments thatScale!Scale to millions oflearnersServe MHE as well as third-partycontentIncludingopen contentSupportlearning apps010100100111010101010101001010101010Self-adapt viausage dataThe Problem
    13. 13. • Allow for elastic scaling under spike periods• Ability to catalog & deliver content from manysources• Consistent low-latency for metadata and stats access• Require full-text search support for contentdiscovery• Offer tunable content ranking & recommendationfunctionsBackend is an Interactive Content Delivery Cloud that must:XML DatabasesSQL/MR EnginesIn-memory Data GridsEnterprise Search ServersExperimented with a combination of:The Challenge
    14. 14. The Learning Portal• Designed and built as acollaboration between MHE Labsand Couchbase• Serves as proof-of-concept andtesting harness for Couchbase +Elasticsearch integration• Available for download andfurther development as opensource codehttps://github.com/couchbaselabs/learningportal
    15. 15. • Document Modeling• Metadata & Content Storage• View Querying to support Content Browsing• Elasticsearch Integration (Full Text Search)- Content Updated in near Real-Time- Search Content Summaries- Relevancy boosted based on User Preferences• Real-Time Content Updates• Event Logging for offline analysisTechniques Used
    16. 16. Couchbase 2.0 + ElasticsearchStore full-text articles as wellas document metadata forimage, video and text content inCouchbaseCombine user preferencesstatistics with customrelevancy scoring to providepersonalized search resultsLogs user behavior to calculateuser preference statistics (e.g.video > text)12 4Continuously accept updatesfrom Couchbase with newcontent & stats3
    17. 17. Data ModelContent MetadataBucketUser ProfilesBucketContent StatsBucket• Stores content metadata formedia objects and content forarticles• Includestags, contributors, typeinformation• Includes pointer to the media• Stores user view details pertype• Updated every time a userviews a doc with running count• To be used for customizing ESsearch results per userpreference• Stores content view details• Updated for every time adocument is viewed• To be used for boosting ESsearch results based onpopularity
    18. 18. Architecture
    19. 19. • User account information• User game profile info• User’s social graph• State of the game• Player badges and statsSocial and Mobile GamingUse Case: Social Gaming• Ability to support rapid growth• Fast response times for awesomeuser experience• Game uptime –24x7x365• Easy to update apps with newfeatures• Scalability ensures that games are ready to handle the millions ofusers that come with viral growth.• High performance guarantees players are never left waiting tomake their next move.• Always-on operations means zero interruption to game play (andrevenue)• Flexible data model means games can be developed rapidly andupdated easily with new featuresTypes of Data Application RequirementsWhy NoSQL and Couchbase
    20. 20. Social gaming atTencent Stomp Games
    21. 21. Use Case: Social gamingBuilding a social game with anawesome user experience thatcan scale to millions of players
    22. 22. Social gaming is all about the experienceApplications needs- User centric data (read key-value access)- Scalability- Easy and simple backendThe Problem
    23. 23. • Must be scalable• Highly available• Extreme performance (latency and throughput)• Cost effective• Operationally easy to maintainBackend must be a platform for multiple gamesThe Challenge
    24. 24. The architecture
    25. 25. • Social media feeds:Twitter, Facebook, LinkedIn• Blogs, news, press articles• Data service feeds:Hoovers, Reuters3rd Party Data AggregationUse Case: 3rd party data aggregation• Flexibility to store any kind ofcontent• Flexibility to handle schemachanges• Full-text Search across data set• High speed data ingestion• Scales horizontally as more contentgets added to the system• JSON provides schema flexibility to store all types of content andmetadata• Fast access to individual documents via built-in cache, high writethroughput• Indexing and querying provides real-time analytics capabilities acrossdataset• Integration with Elasticsearch for full-text search• Ease of scalability ensures that the data cluster can be grownseamlessly as the amount of user and ad data growsTypes of Data Application RequirementsWhy NoSQL and Couchbase
    26. 26. 3rd party data aggregation atSambacloud
    27. 27. Use Case: 3rd party data aggregationBuilding a data and contentaggregation and managementplatform
    28. 28. More and more data and content coming in from externalsources: social media, data services, press andnews, blogsRequire a single content store for all this information to handledifferent types of formats and schemasThe Problem
    29. 29. • Flexible data model to handle any schema andconstant changes to schemas• Allow for elastic scaling particularly for cloudenvironments• Consistent low-latency access and ability to handleincoming streams• Require full-text search support for content• Light weight analytics for sorting / rankingThe platform must supportThe Challenge
    30. 30. The TechnologiesWorkAgile ProjectsShareAny ContentOrganizeChannelsRecommendAnalyticsSambaCloud Content Services – REST API, HTML5
    31. 31. • Application objects• Popular search queryresults• Session information• Heavily accessed weblanding pagesHigh availability cachingUse Case: High availability caching• Consistently low response timesfor document / key lookups• High-availability - 24x7x365• Operationally easy to migrate /upgrade / maintain with apponline• Replacement for entire cachingtier• Low latency in sub-milliseconds with consistently high read /write throughput• Always-on operations even for database upgrades andmaintenance with zero down time• memcached compatibility for easy migration to Couchbasewithout any application changes• High availability and disaster replication with intra-cluster andcross-cluster replication (XDCR)Types of Data Application RequirementsWhy NoSQL and Couchbasehttp://www.couchbase.com/memcached
    32. 32. • User profile: preferencesand psychographic data• Ad serving history by user• Ad buying history byadvertiser• Ad serving history byadvertiserAd TargetingUse Case: Ad Targeting• High performance to meetlimited ad serving budget; timeallowance is typically <40 msec• Scalability to handle hundreds ofmillions of user profiles andrapidly growing amount of data• 24x7x365 availability to avoid adrevenue loss• Sub-millisecond reads/writes means less time is needed for dataaccess, more time is available for ad logic processing, and morehighly optimized ads will be served• Ease of scalability ensures that the data cluster can be grownseamlessly as the amount of user and ad data grows• Always-on operations = always-on revenue. You will never missthe opportunity to serve an ad because downtime.Types of Data Application RequirementsWhy NoSQL and Couchbasehttp://www.couchbase.com/ad_platforms
    33. 33. • User profile information• User registration data• Logins and credentialsUser Profile StoreUse Case: User Profile StoreKey value data access with thefollowing properties :• Strong consistency• Scalability to handle hundreds ofmillions of user profiles and therapidly growing number of users• 24x7x365 availability to avoidany disruptions• Strong consistency in the clusters means that a data readfollowing a particular write will return the previously written datavalue. There are no quorum reads.• The cluster must be able to scale out to store data for millions ofusers who access the system concurrently.• The cluster needs to be highly available 24/365. Within acluster, data should be replicated and the cluster must be onlineeven in the event of a failover. Using active-active crossdatacenter replication, data should be replicated acrossdatacenters for disaster recovery and for locality.Types of Data Application RequirementsWhy NoSQL and Couchbasehttp://blog.couchbase.com/couchbase-nosql-tunewiki-billion-documents-and-counting
    34. 34. Questions?
    35. 35. Thank youdon@couchbase.com@NoSQLDon

    ×