How Companies use
NoSQL and Couchbase
Dipti Borkar
Director, Product Management
Anil Kumar
Product Management
Two kinds of Database Management
System

OLTP / OLTP like
Operational Stores

Data warehouse or
Analytics system
NoSQL + Big Data

Operational database for
web and mobile apps with
high performance at scale

Map-reduce against
huge dat...
Common Use Cases
Social Gaming
• Couchbase stores
player and game
data
• Examples
customers include:
Zynga
• Tapjoy, Ubiso...
Use Case: High-Availability Caching
High availability caching

User Requests

Application Layer
Read-Write
Requests

Cache...
Use Case: High-Availability Caching
Data Cached in Couchbase?

Application characteristic

• Application objects

• Speed ...
Use Case: High-Availability Caching
Why NoSQL?
• Low latency in sub-milliseconds with consistently high read /
write throu...
Use Case: Session Store
Session Store
Use Case: Session Store
Data stored in Couchbase?

Application characteristic

• Session values or Cookies
(stored as key-...
Use Case: Session Store
Why NoSQL?
• Low latency in sub-milliseconds with consistently high read /
write throughput for se...
Use Case: Globally Distributed User Profile
Store
User ID / Profile Store
Use Case: Globally Distributed User Profile
Store
Data stored in Couchbase?

Application characteristic

• User profile wi...
Use Case: Globally Distributed User Profile
Store
Why NoSQL?
• Low latency and high throughput for very quick lookups for
...
Use Case: Data Aggregation
Data Aggregation
Use Case: Data Aggregation
Data stored in Couchbase?

Application characteristic

• Social media feeds:
Twitter, Facebook,...
Use Case: Data Aggregation
Why NoSQL?
• JSON provides schema flexibility to store all types of content
and metadata
• Fast...
Use Case: Content and Metadata Store
Data Aggregation
Use Case: Content and Metadata Store
Data stored in Couchbase?

Application characteristic

• Content metadata

• Flexibil...
Use Case: Content and Metadata Store
Why NoSQL?
• Fast access to metadata and content via object-managed
cache
• JSON prov...
McGraw Hill Education Labs
Learning portal
Use Case: Content and metadata store
Building a selfadapting, interactive learning
portal with Couchbase
The Problem
As learning move online in great numbers

Growing need to build interactive learning environments that
0101001...
The Challenge
Backend is an Interactive Content Delivery Cloud that must:
•

Allow for elastic scaling under spike periods...
Architecture
LivePerson – Real time visitor
engagement
Use Case: 3rd party data aggregation with
analytics

LiveEngage DASHBOARD

Real time Analytics for
LivePerson's customers
LivePerson: Leading customer engagement
platform
The Problem
Requirements Requirements Requirements

•
•
•
•
•
•

13
VOLUME

High throughput, really fast

Linear scale
Sea...
Architecture
Application server
Tomcat

REST API

Couchbase Java SDK

cluster

cluster

XDCR
M/R views

M/R views

Storm T...
Questions?
Thank you!

dipti@couchbase.com
How companies-use-no sql-and-couchbase-10152013
Upcoming SlideShare
Loading in...5
×

How companies-use-no sql-and-couchbase-10152013

837

Published on

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

  • Be the first to like this

No Downloads
Views
Total Views
837
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
25
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

How companies-use-no sql-and-couchbase-10152013

  1. 1. How Companies use NoSQL and Couchbase Dipti Borkar Director, Product Management Anil Kumar Product Management
  2. 2. Two kinds of Database Management System OLTP / OLTP like Operational Stores Data warehouse or Analytics system
  3. 3. NoSQL + Big Data Operational database for web and mobile apps with high performance at scale Map-reduce against huge datasets to analyze and find insights and answers
  4. 4. Common Use Cases Social Gaming • Couchbase stores player and game data • Examples customers include: Zynga • Tapjoy, Ubisoft, Ten cent Mobile Apps • Couchbase stores user info and app content • Examples customers include: Kobo, Playtika Ad Targeting • Couchbase stores user information for fast access • Examples customers include: AOL, Mediamind, Co nvertro Session store • Couchbase Server as a keyvalue store • Examples customers include: Concur, Sabre User Profile Store • Couchbase Server as a key-value store • Examples customers include: Tunewiki High availability cache • Couchbase Server used as a cache tier replacement • Examples customers include: Orbitz Content & Metadata Store • Couchbase document store with Elastic Search • Examples customers include: McGraw Hill 3rd party data aggregation • Couchbase stores social media and data feeds • Examples customers include: LivePerson
  5. 5. Use Case: High-Availability Caching High availability caching User Requests Application Layer Read-Write Requests Cache Misses and Write Requests Couchbase Distributed Cache RDBMS
  6. 6. Use Case: High-Availability Caching Data Cached in Couchbase? Application characteristic • Application objects • Speed up RDBMS • Popular search query results • Consistently low response times for document / key lookups • Session information • Heavily accessed web landing pages • High-availability 24x7x365 • Replacement for entire caching tier
  7. 7. Use Case: High-Availability Caching Why NoSQL? • Low latency in sub-milliseconds with consistently high read / write throughput using built-in cache • Always-on operations even for database upgrades and maintenance with zero down time
  8. 8. Use Case: Session Store Session Store
  9. 9. Use Case: Session Store Data stored in Couchbase? Application characteristic • Session values or Cookies (stored as key-value pairs) • Extremely fast access to session data using unique session ID • Examples include: items in a shopping cart, flights selected, search results, etc. • Easy scalability to handle fast growing number of users and user-generated data • Always-on functionality for global user base
  10. 10. Use Case: Session Store Why NoSQL? • Low latency in sub-milliseconds with consistently high read / write throughput for session data via the built-in object-level cache • Linear throughput scalability to grow the database as user and data volume grow • Always-on operations even particularly high availability using Couchbase replication and failover • Intra cluster and cross cluster (XDCR) replication for globally distributed active-active platform
  11. 11. Use Case: Globally Distributed User Profile Store User ID / Profile Store
  12. 12. Use Case: Globally Distributed User Profile Store Data stored in Couchbase? Application characteristic • User profile with unique ID • Extremely fast access to individual profiles • User setting / preferences • User’s network • User application state • Always online system as multiple applications access user profiles • Flexibility to add and update user attributes • Easy scalability to handle fast growing number of users
  13. 13. Use Case: Globally Distributed User Profile Store Why NoSQL? • Low latency and high throughput for very quick lookups for millions of concurrent users using built-in cache • Intra cluster and cross cluster (XDCR) replication for high availability and disaster recovery • Active-active geo-distributed system to handle globally distributed user base • Online admin operations eliminate system downtime
  14. 14. Use Case: Data Aggregation Data Aggregation
  15. 15. Use Case: Data Aggregation Data stored in Couchbase? Application characteristic • Social media feeds: Twitter, Facebook, LinkedI n • Flexibility to store any kind of content • Blogs, news, press articles • Flexibility to handle schema changes • Data service feeds: Hoovers, Reuters • Full-text Search across data set • Data form other systems • High speed data ingestion • Scales horizontally as more content gets added to the system
  16. 16. Use Case: Data Aggregation Why NoSQL? • JSON provides schema flexibility to store all types of content and metadata • Fast access to individual documents via built-in cache, high write throughput • Indexing and querying provides real-time analytics capabilities across dataset • Integration with ElasticSearch for full-text search • Ease of scalability ensures that the data cluster can be grown seamlessly as the amount of user and ad data grows
  17. 17. Use Case: Content and Metadata Store Data Aggregation
  18. 18. Use Case: Content and Metadata Store Data stored in Couchbase? Application characteristic • Content metadata • Flexibility to store any kind of content • Content: Articles, text • Landing pages for website • Digital content: eBooks, magazine, researc h material • Fast access to content metadata (most accessed objects) and content • Full-text Search across data set • Scales horizontally as more content gets added to the system
  19. 19. Use Case: Content and Metadata Store Why NoSQL? • Fast access to metadata and content via object-managed cache • JSON provides schema flexibility to store all types of content and metadata • Indexing and querying provides real-time analytics capabilities across dataset • Integration with ElasticSearch for full-text search • Ease of scalability ensures that the data cluster can be grown seamlessly as the amount of user and ad data grows
  20. 20. McGraw Hill Education Labs Learning portal
  21. 21. Use Case: Content and metadata store Building a selfadapting, interactive learning portal with Couchbase
  22. 22. The Problem As learning move online in great numbers Growing need to build interactive learning environments that 0101001001 1101010101 0101001010 101010 Scale! Scale to millions of learners Serve MHE as well as third-party content Including open content Support learning apps Self-adapt via usage data
  23. 23. The Challenge Backend is an Interactive Content Delivery Cloud that must: • Allow for elastic scaling under spike periods • Ability to catalog & deliver content from many sources • Consistent low-latency for metadata and stats access • Require full-text search support for content discovery • Offer tunable content ranking & recommendation functions Experimented with a combination of: XML Databases In-memory Data Grids SQL/MR Engines Enterprise Search Servers
  24. 24. Architecture
  25. 25. LivePerson – Real time visitor engagement
  26. 26. Use Case: 3rd party data aggregation with analytics LiveEngage DASHBOARD Real time Analytics for LivePerson's customers
  27. 27. LivePerson: Leading customer engagement platform
  28. 28. The Problem Requirements Requirements Requirements • • • • • • 13 VOLUME High throughput, really fast Linear scale Searchable (Views and M/R) Supports both K/V & Document store Cross data center replication “Always on”, Resilience solution TB per month 1 ~ PB In total 1.8 B Visits per month
  29. 29. Architecture Application server Tomcat REST API Couchbase Java SDK cluster cluster XDCR M/R views M/R views Storm Topology Storm Topology Couchbase Java SDK Couchbase Java SDK
  30. 30. Questions?
  31. 31. Thank you! dipti@couchbase.com
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×