The Modern Database for Enterprise Applications

Confidential and Proprietary. Do not distribute without Couchbase consent. © Couchbase 2021. All rights reserved.
Gregor Bauer
Manager Solutions Engineering CEUR
gregor@couchbase.com
2.2.2023
The Modern Database for
Enterprise Applications

1. Requirements for Modern DBMS
2. Microservices need Speed AND Flexibility
3. Distributed Cloud Deployment
4. Demo
Agenda

Confidential and Proprietary. Do not distribute without Couchbase consent. © Couchbase 2022. All rights reserved. 3
1Requirements for
Modern DBMS

Customers Tell Us: Application Requirements Have Changed
Deliver Great Experiences
• Personalized & responsive
• Anywhere & everywhere
• Real time info & inventory
• Ensuring dependable transactions
Develop Efficiently
• Simplify & accelerate development
• Tap my skills (SDKs & SQL)
• Support best practices
• Avoid data sprawl
Deploy Effectively
• Support hybrid clouds, Edge, 5G
• 100% uptime & global scale
• Flexible management options
• Cost effective

Innovation Leaders
15k
mobile sensors per voyage
100’s M
operations per/day
City-at-sea experience via IoT
& edge-based mobile devices
Global fraud detection
and prevention
3B+
payment accounts protected
65%
of world’s card accounts
Product catalog, pricing,
shopping cart, daily deals,
inventory management
4,000
stores worldwide
1.6B
rules applied in real-time
High performance
caching for social
network
10M+
requests / second
800M+
users

Proven, Mission Critical Applications by Industry Leaders
Retail & E-
Commerce
Travel &
Hospitality Telecom Gaming
Financial
Services Healthcare
Media &
Entertainment Industrial IoT
3 of the Top 10
eCommerce
Companies
6 of the Top 10
Broadcast Companies
3 of the Top 3
GDS
Companies
6 of the Top 10
Online Casino
Gaming Companies
3 of the Top 3
Credit Reporting
Companies
3 Fortune 500
Healthcare
Companies
2 of the Top 2
IoT
Platforms

BI & Big Data
Document Store
Frontend/Backend Cache
Mobile & Edge
Helping Customers Across Uses Cases & Business Goals
BI & Big Data
Document Store
Frontend/Backend
Mobile & Edge
Real-time
Analytics
Personalization
Token
Management
Mobile
Application
Product Catalog
Transaction
Processing
Fraud Detection
Risk Analysis
Customer 360
Legacy
Offloading
Field Service
Enablement
Edge
Computing
Business Goals
• Increase customer
satisfaction
• Faster time to market
• Drive loyalty, increase
revenues
• Increase cost savings
• Lower total cost of
ownership
• Reduce cart abandonment

2Microservices need
Speed AND Flexibility

JSON is Flexible, its Structure can be Changed by the App
“Developers can now take ownership and change business rules on the fly, without
having to rebuild the app. This lets us focus on what we actually have to do.”
Joaquim Olivera
Head of Mobile Development
Ryanair
• Doc format aligns to application needs
• Less joins than RDBMS, improving performance
{
“UserID”: “1”,
“firstName”:”Jeffrey”,
“lastName”: “Mackay”,
“skills”: [”SQL”, “JavaScript”,
“NoSQL”]
“experience”: [
{
“role”: “Solutions Architect”,
“company”: “AppMax Inc”,
},
{
“role”: “Solutions Engineer”,
“company”: “Couchbase”,
}
]
}
JSON Document
Relational
Tables
ID First Last
USERS
1 Jeffrey Mackay
1 JavaScript
1 NoSQL
1 SQL
USER_SKILLS
UserID Skill Name
ID Role Company
USER_EXPERIENCE
1 Solutions Architect AppMax Inc
1 Solutions Engineer Couchbase
1
JSON is great for changing dynamic user profiles and complex catalog entries

Data Access: SQL++
SELECT *
FROM users
WHERE users.lastName = “Johnson”
UPDATE users
SET status = “Platinum”
WHERE users.lastName = “Johnson”
DELETE
FROM users
WHERE users.firstName = “Shane”
Create User
Get User
Update User
Delete User
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
INSERT INTO
VALUES
Users (KEY, VALUE)
(
“user::100”,
{
“firstName”: ”Shane”,
“lastName”: ”Johnson”
}
);

Simplistic View: Data Management For Applications
Database
Infrastructure
Functional
Requirements
Application

Reality: Data Sprawl & Management Challenges
Mobile/Edge Apps
Applications and Microservices
Cache
NoSQL
Database
Relational
Database
Query
tools
Full Text
Search
Eventing Analytics Mobile
Infrastructure layers

How is Couchbase Different?
Mobile/Edge Apps
Applications and Microservices
Fast
• Memory-first design
• Cloud-native scale
• Geo-replication via XDCR
• HA, DR & backup
• Low latency Cloud to Edge
Familiar
• SQL++ query language
• Dynamic Schema
• ACID SQL Transactions
• Cost-based optimizer
• SDKs for 12+ languages
Affordable
• Elastic scaling, sharding &
rebalancing
• Multidimensional scaling
• High-density storage
• Incredible price/performance
Flexible
• JSON document
• Multimodel services
• Cloud deploy anywhere
• Mobile & Edge ready
SQL
Integrated
Cache
JSON
Documents
SQL
Query
Full Text
Search
Operational
Analytics
Eventing
Key-Value
Access
Geo-Replication
& Sync
Mobile
Database
Relational
Capabilities

How is Couchbase Different?

Couchbase Products
Couchbase Lite Sync Gateway Couchbase Server
SYNC
GATEWAY
Couchbase Autonomous Operator
Couchbase Capella (DBaaS)

3Distributed Cloud
Deployment

Workload Isolation: Optimize Service Performance to Hardware
Deploy
Develop
Query
Indexing
Data
Analytics
Full Text
Eventing
NODE
1
NODE
13
Cluster Manager
Full Text
NODE
2
NODE
3
NODE
4
NODE
5
NODE
6
NODE
7
NODE
12
NODE
9
NODE
10
NODE
11
NODE
8
Query
Indexing Data Analytics
Eventing
“The most important thing for our evaluation process was the multi-dimensional scaling.
Having nodes for specific use cases is very powerful.”
Jay Duraisamy
SVP, USIS Engineering
Equifax

High Availability and Durability: Always-On Reliability
“To set up a resilient implementation took us minutes. We stood up servers,
lit them up, balanced the load, and instantly we were resilient.”
Robert Lawrence
Prod. Owner, Digital Catalysts
PG&E
• Continuous replication
• Auto failover recovery
• No-disruption upgrade
• Speedy rebalancing
• Data center replication
across clusters
• Auto sharding
Continuous Replication
App Server
Client library
cluster map
ACTIVE
REPLICA
ACTIVE
REPLICA
1
ACTIVE
REPLICA
App Server
Client library
cluster map
ACTIVE
REPLICA
2
Node Loss: Failed Server
ACTIVE
REPLICA
App Server
Client library
cluster map
ACTIVE
REPLICA
Failover Activation
ACTIVE
REPLICA
3
App Server
Client library
cluster map
ACTIVE
REPLICA
ACTIVE
REPLICA
Restored Cluster
ACTIVE
REPLICA
4

Wherever Data is Needed: Globally, to the Edge, and in Device
Data
Center
Gateway
• Low latency to the Edge
• Peer–to-peer syncing
Replication Service Mobile Service
Active DC
Standby DC
All
data
Data
subset
All
data
Active DC
“There are many key factors for choosing Couchbase:
scalability, high availability, and XDCR to name a few.”
Krishnan Venkatasubramanian
Head of IT Architecture
Sky

Cloud-Native Database Automation Requirements
Increasing the speed of delivery of
database changes and freeing
developers up to do more value
added work are the key drivers for
automating the delivery of database
changes.
Standardization of Development
and Production Environment.
Standardization of Cloud
Infrastructure. Elastic Scalability
and Cost Effective.
Reduce your DevOps workload by
running an autonomous, fully
managed stateful database
application.
Run, manage, and scale database
next to microservices applications
as a data service on the same
Kubernetes platform.
DATABASE
AUTOMATION

Autonomous Operator

Couchbase Operator
Capabilities
Automated cluster configuration and provisioning
Cluster life-
cycle
Auto-scaling of Couchbase services
Automated cluster upgrade
Auto-recovery of Couchbase services
Cluster hibernation
Certified persistent volumes
Cluster
configuration
Automated Couchbase server groups
Automated cross data center replication (XDCR)
TLS and certificate rotation
User and group management
Automated Backup and Restore Management
Centralized logging with FluentBit
Centralized Monitoring using Prometheus & Grafana

Challenge 1: Eliminate database siloes
● Stateless microservices are deployed as
containers and orchestrated with
Kubernetes
● Managing state in a distributed application
is hard. When you throw multiple layers of
abstraction and elastic scaling into the mix,
it gets even harder.
● Kubernetes is great at managing compute
and memory resources but storage was not
something managed by Kubernetes directly.
● The typical pattern was to host your
database elsewhere.
Kubernetes

Challenge 2: Avoid cloud vendor lock-in
● Switching between cloud providers is
a major challenge because there is no
industry standardization.
● Increased data management
complexity and overhead become
even more complicated when data
sets are deployed across hybrid or
multiple cloud providers:
○ Deployment over multiple clouds
○ Upgrade multiple clusters
○ Synchronization of data

Challenge 3: Lower operational costs
● A typical day in the life of an operations/DevOps engineer involves provisioning, scaling,
configuring, and upgrading 100's of distributed database systems.

4Demo

THANK YOU

The Modern Database for Enterprise Applications

More Related Content

What's hot

Similar to The Modern Database for Enterprise Applications

More from QAware GmbH

Recently uploaded

The Modern Database for Enterprise Applications