High Performance with Distributed Caching Key Requirements For Choosing The Right Solution High Performance with Distributed Caching: Key Requirements for Choosing the Right Solution

Table of Contents

Executive summary 3 Companies are choosing Couchbase for their caching layer, and much more 3 Memory-first 4 Persistence 4

Elastic scalability 4 Replication 5 More than caching 5 About this guide 5

Memcached and – two popular caching solutions 6 Oracle Coherence 6 6

Why ? Better performance, lower costs 6 Common caching use cases 7

Key requirements for an effective distributed caching solution 8 Problems with Oracle Coherence: cost, complexity, capabilities 8 Memcached: A simple, powerful open source cache 10 Lack of enterprise support, built-in management, and advanced features 10

Couchbase Server as a high-performance 10 General-purpose NoSQL with Memcached roots 10 Meets key requirements for distributed caching 11 Develop with agility 11 Perform at any scale 11 Manage with ease 12 Benchmarks: Couchbase performance under caching workloads 12

Simple migration from Oracle Coherence or Memcached to Couchbase 13 Drop-in replacement for Memcached: No code changes required 14

Migrating from Oracle Coherence to 14

Beyond caching: Simplify IT infrastructure, reduce costs with Couchbase 14 About Couchbase 14 Caching has become Executive Summary a de facto technology to boost application For many web, mobile, and Internet of Things (IoT) applications that run in clustered performance as well or cloud environments, distributed caching is a key requirement, for reasons of both as reduce costs. performance and cost. By caching frequently accessed data in memory – rather than making round trips to the backend database – applications can deliver highly responsive experiences that today’s users expect. And by reducing workloads on backend resources and network calls to the backend, caching can significantly lower capital and operating costs.

All distributed caching solutions solve for common problems – performance, manageability, scalability – in order to gain effective access to data in high-quality applications.

Figure 1: The three common requirements for distributed caching solutions

High performance is a given, because the primary goal of caching is to alleviate the bottlenecks that come with traditional . This is not limited to relational databases, however. NoSQL databases like MongoDB™ also have to make up for their performance problems by recommending a third-party cache, such as , to service large numbers of requests in a timely manner.

Caching solutions must be easy to manage, but often are not. Whether it’s being able to easily add a new node, or to resize existing services, it needs to be quick and easy to configure. The best solutions provide graphical user interfaces and REST to help keep things manageable.

Elastic scalability refers not only to the ability to grow a cluster as needed, but also refers to the ability to replicate across multiple wide area cluster networks. Cross datacenter replication is a feature that is either missing or very poor performing across many caching technologies. To achieve this scalability, several products often have to be glued together, thereby decreasing manageability and greatly increasing cost.

Companies are choosing Couchbase for their caching layer, and much more

Couchbase Server is a great fit for many caching scenarios. More than 400 enterprises – including eBay, PayPal, LinkedIn, Intuit, Viber, and many others – have deployed Couchbase Server for mission-critical applications. So why have they chosen Couchbase

3 over the alternatives? It’s not only for the caching capabilities but also for other powerful features, a few of which are described here.

Caching solutions are built to solve the problems mentioned above. Many are merely key-value stores with in-memory capabilities and some ability to scale out. However, their overall architecture prevents them from being much more than that.

Couchbase was architected to solve the core problems that are often related to caching but are really just standard performance and scalability issues. Additionally, Couchbase addresses challenges relating to high availability for applications as well as comprehensive durability for data with failover options.

There are four particular capabilities that are core to Couchbase and that serve as the foundation for all the other capabilities of the database.

Memory-first

Couchbase has a memory-first architecture – it can run as a pure in-memory database, letting applications get the fastest possible access to data without hitting a disk. It can also service data beyond the size of memory, using efficient data access methods that keep memory loaded with the latest updates. Couchbase is a high-performance and flexible caching solution that makes the most out of the resources that are available on each node.

Incidentally, it is also an easy upgrade for those moving from Memcached – they can simply drop-in Couchbase as a full replacement and instantly gain several advantages while also maintaining in-memory performance as well as adding many other advantages.

Persistence

Although in-memory capabilities are available, that does not mean that Couchbase only operates in memory. Eventual data persistence is integral to Couchbase and provides the added benefit of data durability that enterprises demand.

For those who are simply using Couchbase as a cache, they benefit from not having to reload the cache every time they either need to adjust their infrastructure or respond to a system failure – the data remains available as expected.

Elastic scalability

In-memory caching solutions should not require you to scale up your hardware to keep pace with your data volumes. Couchbase allows you to easily scale out your cluster with commodity hardware when you want to share the workload or distribute data resources. Enterprise users demand this functionality as it minimizes infrastructure expenditures.

Similarly, different kinds of workloads in Couchbase can be isolated from each other depending on need. If you need to improve performance for one aspect of Couchbase, for example the query service capabilities, then you only need to add more query nodes. Likewise, if you have more data but don’t need to scale querying capabilities, you can selectively add more data nodes.

This is referred to as Multi-Dimensional Scaling (MDS) and allows users to isolate their workloads while also incrementally increasing access to more cluster resources as needed. Other solutions require you to overprovision new hardware resources in anticipation of future problems, but that is not required with Couchbase.

4 Replication

When you combine the in-memory, elastic scalability, and persistence capabilities of Couchbase you have a very powerful platform. But today’s enterprise demands require even more.

In order to service the high availability needs of large users, a solution for replicating not only across multiple nodes, but also across multiple clusters, is required.

Intra-node replication is done at the speed of memory and local persistence of replicated data is performed rapidly. Couchbase also offers intra-cluster replication that is very efficient and serves as a way to keep data both highly available and local to application servers in different geographic regions.

Cross datacenter replication (XDCR) is one of the most powerful features of Couchbase, and is easy to use and set up through a graphical web administration console. Varying types of replication topologies – including master-master – are supported, providing many options for keeping data highly available and easy to access.

More than caching

When you combine all the above architectural advantages of Couchbase you have the most comprehensive, high-performance NoSQL database platform to build on top of. While caching is an obvious use case to get started, there is so much that is possible once your data is in Couchbase. By caching frequently Other features include SQL-like querying using the Couchbase NoSQL used data in memory (N1QL) – effectively letting you query JSON data without having to enforce a schema or – rather than making database round trips transform your data to behave a certain way just to get answers to queries. and incurring disk io More advanced real-time analytic queries are also possible as well as full-text searches. overhead – application Many developer-centric features exist in Couchbase, from server-side event processing, response times can be dramatically improved, operation tracing, and automatic application failover between clusters. typically by orders of These are all features that the most demanding enterprises require for effective data magnitude. management. The remainder of this paper explores these concepts further and contrasts them with other solutions within the overall context of caching solutions.

About this guide

Based on Couchbase’s experience with leading enterprises, this guide:

• Explains the value of caching and common caching use cases

• Details the key requirements for an effective, highly available distributed cache

• Explains differences in capabilities across Oracle Coherence, Memcached, and Couchbase Server

• Describes how Couchbase Server provides a high-performance, low-cost, and easy-to- manage caching solution

5 Memcached and Oracle Coherence – two popular caching solutions

Memcached and Oracle Coherence are a small part of a larger ecosystem of key-value databases and caching solutions. Many other caching-related solutions exist, including Redis, GemFire, , and more. They attempt to solve for similar problems but do not particularly aim to be a comprehensive database solution to service caching or other use cases that a NoSQL offering needs to have. This paper will focus on Memcached and Oracle Coherence, however, the architectural considerations apply to all NoSQL databases and caching solutions.

Oracle Coherence

For businesses that run on Oracle databases, Coherence is often the default caching product. But many companies find that Oracle Coherence isn’t the best caching solution for every use case, so they seek out other products. The typical complaints with Oracle Coherence are its high cost, complexity, limited data size per node, and lack of key features like cross datacenter replication and workload isolation for specific features running on certain nodes.

Memcached

At the other end of the spectrum, Memcached is a free open source product that’s used in thousands of web, mobile, and IoT applications around the world. It’s simple to install and deploy, and it delivers reliable high performance. However, Memcached has no enterprise support available, nor does it include a management console for easy monitoring. And many companies that deploy Memcached find they want additional capabilities not included in Memcached, such as more sophisticated availability features.

Couchbase has some shared lineage with Memcached and addresses many of its limitations while also serving as a complete document database solution.

The use of a cache Why cache? Better performance, lower costs should not place undue burden on the Today’s web, mobile, and IoT applications need to operate at internet scale: thousands to operations team. It millions of users, terabytes (sometimes petabytes) of data, sub-millisecond response times, should be reasonably multiple device types, and global reach. To meet these requirements, modern applications quick to deploy and are built to run on clusters of commodity servers in distributed environments, easy to monitor and either in enterprise datacenters or on public clouds such as (AWS) manage: set it and or (GCP). forget it. Caching has become a de facto technology to boost application performance as well as reduce costs. By caching frequently used data in memory – rather than making database round trips and incurring disk IO overhead – application response times can be dramatically improved, typically by orders of magnitude.

In addition, caching can substantially lower capital and operating costs by reducing workloads on backend systems and reducing network usage. In particular, if the application runs on a relational database like Oracle – which requires high-end, costly hardware in order to scale – a distributed, scale-out caching solution that runs on low-cost commodity servers can reduce the need to add expensive resources.

6 APPLICATION TIER APPLICATION TIER

APP APP ... APP APP APP ... APP

DATA ACCESS LAYER DATA ACCESS LAYER

1 2 3

CACHE DATABASE CACHE DATABASE

RAM RAM ... RAM ... RAM RAM ... RAM ...

1 Write to cache and database. 2 Read from cache.

3 If no longer cached, read from database.

Figure 2: High-level database cache architecture

Common caching use cases

Due to clear performance and cost benefits, caching is used across numerous applications and use cases, including:

• Speeding up RDBMS: Many web and mobile applications need to access data from a backend relational database management system (RDBMS) – for example, inventory data for an online product catalog. However, relational systems were not designed to operate at internet scale, and can be easily overwhelmed by the volume of requests from web and mobile applications, particularly as usage grows over time. Caching data from the RDBMS in memory is a widely used, cost-effective technique to speed up the backend RDBMS.

• Managing usage spikes: Web and mobile applications often experience spikes in usage (for example, seasonal surges like Black Friday and Cyber Monday, or when a video goes viral, etc.). In these and others cases, caching can prevent the application from being overwhelmed and can help avoid the need to add expensive backend resources.

• Mainframe offloading: Mainframes are still widely used in many industries, including financial services, government, retail, airlines, and heavy manufacturing, among others. A cache is used to offload workloads from a backend mainframe, thereby reducing MIPS costs (i.e., mainframe usage fees charged on a “millions of instructions per second” basis), as well as enabling completely new services otherwise not possible or cost prohibitive utilizing just the mainframe.

• Token caching: In this use case, tokens are cached in memory in order to deliver high- performance user authentication and validation. eBay, for example, deploys Couchbase Server to cache token data for its buyers and sellers (over 100 million active users globally, who are served more than 2 billion page views a day).

• Web session store: Session data and web history are kept in memory – for example, as inputs to a shopping cart or real-time recommendation engine on an e-commerce site, or player history in a game.

7 Key requirements for an effective distributed caching solution

The requirements for an effective caching solution are fairly straightforward. Enterprises generally factor six key criteria into their evaluation. How you weight them depends on your specific situation.

• Performance: Performance is the No. 1 requirement. Specific performance requirements are driven by the underlying application. For a given workload, the cache must meet and sustain the application’s required steady-state performance targets for latency and throughput. Efficiency of performance is a related factor that impacts cost, complexity, and manageability. How much hardware (RAM, servers) is needed to meet the required level of performance? Obviously less is better.

• Scalability: As the workload increases (e.g., more users, more data requests, more operations), the cache must continue delivering the same steady-state performance. The cache must be able to scale linearly, easily, affordably, and without adversely impacting application performance and availability.

• Availability: Data needs to be always available during both unplanned and planned interruptions, whether due to hardware failure or scheduled system maintenance, so the cache must ensure availability of data 24x365.

• Manageability: The use of a cache should not place undue burden on the operations team. It should be reasonably quick to deploy and easy to monitor and manage: set it and forget it.

• Simplicity: All other things equal, simplicity is always better. Adding a cache to your deployment should not introduce unnecessary complexity or make more work for developers.

• Affordability: Cost is always a consideration with any IT decision, both upfront implementation as well as ongoing costs. Your evaluation should consider total cost of ownership, including license fees as well as hardware, services, maintenance, and support.

Problems with Oracle Coherence: cost, complexity, capabilities

Oracle Coherence is recognized as a product that works reasonably well when properly installed, configured, tuned, and maintained. Companies that run Oracle databases typically default to Coherence for caching, but many are not entirely satisfied with it. The main complaints with Oracle Coherence include:

• Complexity: An Oracle Coherence deployment consists of application nodes, data nodes, a management node, an MBean server, a Management Server, an , Enterprise Manager and Enterprise Manager agent, Extend proxies, and more. Significant expertise is needed to configure Oracle Coherence, often requiring expensive consulting services. In contrast to less complex solutions like Couchbase Server – which a developer can easily install with no sysadmin help, and a Couchbase cluster can be up and running in minutes – deploying Oracle Coherence is slow and complicated.

8 The trend in enterprise • Difficult to scale: Oracle Coherence it architecture is requires substantial manual effort toward adopting and downtime to scale. Key open source software tasks, such as adding a node and END USER wherever possible, to rebalancing, are not fully automated. help reduce risk, avoid REPORTING ENTERPRISE vendor lock in, lower • Lacks built-in features like cross XML DEFINITIONS MANAGER costs, and benefit from datacenter replication: Despite its community-driven complexity, Oracle Coherence lacks SQL contributions and some important built-in capabilities. innovation. For example, Oracle Coherence ORACLE RDBMS does not have integrated cross

datacenter replication. Instead, SQL it’s either up to the application to implement it using various hooks, ORACLE MGMT SERVER (OMS) or else customers need to install,

configure, and manage an additional HTTP Oracle product (GoldenGate) if they want replication across datacenters TARGET – METADATA AND XML EM AGENT resulting in additional cost and COLLECTION FILES

complexity. COHERENCE HARDWARE JMX FETCHLET

COHERENCE J2EE, J2SE MANAGEMENT • Memory limitations: Oracle MBEANSERVER NODE Coherence can store at

most 64GB of data per node TCMP even with journal storage APPLICATION DATA NODES PROXY NODE (RAM + SSD). For many enterprise NODES applications, that’s a tiny amount. As a result, you may need to use far more nodes to handle your data requirements, which adds Figure 3: The complexity of Oracle Coherence more licensing costs as well as architecture, as illustrated here, is a common more complexity and management complaint of users who are not satisfied overhead.

• Proprietary: The trend in enterprise IT architecture is toward adopting open source software wherever possible, to help reduce risk, avoid vendor lock in, lower costs, and benefit from community-driven contributions and innovation. As a closed source proprietary product, Oracle Coherence runs counter to today’s preference for open source solutions.

• High cost: Oracle Coherence, like most other proprietary caching products, is expensive. Customers pay substantial fees for Oracle Coherence – which is licensed on a per-core basis, rather than a per-node basis – on top of their already costly Oracle database licenses. In addition, Oracle Coherence is designed to run on high- end, expensive hardware (e.g., Oracle Exalogic), whereas a number of other solutions (including Couchbase Server) are designed to run on inexpensive, commodity servers.

One big issue that Oracle Coherence customers frequently encounter stems from the Unlimited License Agreement (ULA). While the ULA at first blush looks attractive – once it’s signed, the customer can “freely” use the software everywhere – the result is that Oracle Coherence gets used in projects where it’s not the right fit. When it’s time to renew the ULA, many of these projects cannot justify the cost, so customers start looking for alternative solutions.

9 Customers such as Memcached: A simple, powerful open source cache Amadeus, the largest global distribution Memcached is a simple yet powerful, open source cache used by many companies, system for the travel including YouTube, , Craigslist, Zynga, , , Tumblr, and . It’s industry, run over an in-memory, key-value store for small chunks of arbitrary data (strings, objects) from 1 million operations results of database calls, API calls, or page rendering. per second on Couchbase server. Key advantages of Memcached include:

• High performance: Memcached was engineered as a high-performance, scalable cache. It is capable of delivering the throughput required by very large, internet-scale applications.

• Simplicity: Intentionally designed as a pure, bare-bones cache, Memcached is very simple to install and deploy. Users can set up Memcached quickly and easily.

• Low cost: Licensed under the Revised BSD license, Memcached is free open source software.

Lack of enterprise support, built-in management, and advanced features

No commercial entity provides technical support for Memcached. So if you encounter an issue with Memcached, you need to rely on your own resources or the Memcached community. There is no built-in management console, so users need to build their own tools to monitor its performance.

Memcached was intentionally engineered to only be a high-performance, bare-bones cache, so it does not include advanced features that many enterprises require, such as auto failover, load rebalancing, cross datacenter replication, and automated push-button scaling.

As described below, Couchbase Server builds on and extends the strengths of Memcached – including high performance and simplicity – to deliver a more powerful drop-in replacement for Memcached, and an affordable, less complex, open source alternative to Oracle Coherence.

Couchbase Server as a high-performance distributed cache

Couchbase Server has become an attractive alternative to Oracle Coherence and Memcached, as well as other caching products. It’s the only solution that fully meets the requirements of modern web, mobile, and IoT applications that need to support thousands to millions of users, handle large amounts of data, and provide highly responsive experiences on any device.

For many enterprises, Couchbase Server hits the sweet spot by delivering performance, scalability, and availability, while being easy to deploy and manage. And because it’s open source, Couchbase Server is an affordable choice, with enterprise support available from Couchbase.

General-purpose NoSQL database with Memcached roots

Couchbase Server is a general-purpose, document-oriented NoSQL database and has a strong caching heritage. Couchbase founders include the engineers who designed and built Memcached in 2004 at LiveJournal. LiveJournal was one of the internet’s first social networks, before MySpace and Facebook. LiveJournal faced frequent usage spikes as well as continuously growing workloads that overwhelmed backend resources.

10 To solve those issues, LiveJournal engineers (i.e., the future founders of Couchbase) built Memcached as a high-performance cache that’s “dead simple” to use. While it squarely met the goals for high performance and simplicity, Memcached was not designed as a high availability caching solution, so features like auto failover and cross datacenter replication (XDCR) were not built into the product.

In designing Couchbase Server, the engineers who created Memcached took its best aspects – high performance and simplicity – and extended the technology to incorporate additional capabilities, including high availability and easy manageability.

Meets key requirements for distributed caching

Many of the world’s largest enterprises – including leaders in industries such as retail (Tesco), communications (Verizon, AT&T, Viber), media (DirecTV), e-commerce (eBay, PayPal), social networking (LinkedIn), among others – have deployed Couchbase Server As an open source for multiple use cases, including distributed caching. At these and other enterprises, product, the total Couchbase Server is proven in production to support some of the most demanding cost of ownership of Couchbase is applications. Customers such as Amadeus, the largest global distribution system for typically a fraction the travel industry, run over 1 million operations per second on Couchbase Server, with of proprietary consistent sub-millisecond latency. solutions like Oracle Coherence. Couchbase Server delivers against all key requirements of an effective distributed cache solution providing the following three categories of architectural advantages:

Develop with agility

• Simplicity and ease of development: Couchbase Server’s code is streamlined, compact, and highly efficient with a small footprint. It can be installed and configured in minutes and requires very little time and training to learn. It’s easy for developers to work with through the officially supported SDKs that are available for all common languages (Java, , .NET, Python, PHP, Node.js, Go). Rich integration is available via frameworks and components such as Spring Data, LINQ, and .NET Core.

• No hassle scale out when ready: Couchbase clients do not have to change when a cluster grows in size from development laptop to a multi-node production deployment. No manual re-sharding is required by any application and cluster configuration information is all managed behind the scenes by the topology-aware clients.

Perform at any scale

• High performance: Couchbase Server was purpose built to deliver sustained high- throughput rates in environments, providing consistent sub- millisecond latency and exceptional resource efficiency. In a recent benchmark run on the Google Cloud Platform, Couchbase Server sustained 1.1 million operations per second with median latency of 15 milliseconds, requiring just 50 nodes to achieve that level of throughput. By comparison, the popular open source product Cassandra required 300 nodes to deliver comparable performance.

• Elastic scalability: Couchbase Server is designed to provide linear, elastic scalability for web, mobile, and IoT applications at any scale. Customers such as eBay, PayPal, LinkedIn, AT&T, Viber, and many others serve millions of concurrent users globally. Adding or removing nodes can be done in minutes with push-button simplicity, without any downtime or code changes.

11 • Always-on availability: Couchbase Server is designed to be fault tolerant and highly resilient at any scale, delivering always-on availability in case of hardware failures, network outages, or planned maintenance User Requests windows. The shared-nothing node architecture is the foundation of the distributed system, providing APP APP ... APP high availability features including: auto sharding, data replication, and APPLICATION TIER auto failover. A number of major enterprises have selected Couchbase Server specifically because of its Read-Write Requests uniquely simple and powerful cross Cache Misses and Write datacenter replication (XDCR) Requests capabilities.

Active Active Active Manage with ease

• Push-button manageability: Couchbase Server comes with a Replica Replica Replica RDBMS built-in, robust management console. Replication Operations personnel gain complete COUCHBASE SERVER CLUSTER visibility into the Couchbase deployment through dashboards that track dozens of metrics, as well as the tools to configure and manage the Figure 4: Architecture of deploying a Couchbase deployment. These include Couchbase Server cluster as a caching layer push-button controls for tasks such as add or remove nodes, tune memory, or pause and resume. Many Couchbase customers rave about the level of ease and time saving they get from using the management console.

• Enterprise support: Couchbase is the commercial entity that provides development, support, and services for Couchbase Server. Customers who want an enterprise support subscription can choose from three options (Silver, Gold, and Platinum).

• Affordability: As an open source product, the total cost of ownership of Couchbase is typically a fraction of proprietary solutions like Oracle Coherence, often as much as 80% less. Couchbase Server can be freely downloaded without any license fees, allowing you to prototype and experiment with zero cost or risk. Also, Couchbase Server is designed to run efficiently on low-cost, commodity servers rather than expensive hardware like Oracle Exalogic. And because Couchbase Server is far less complex to deploy and manage, it takes significantly fewer resources to support it.

Benchmarks: Couchbase performance under caching workloads

Couchbase Server supports typical caching use cases, and also supports more challenging document database scenarios as well; in each of these it outperforms the competition.

Benchmark analysis has been performed by third-party consulting company Altoros. They ran various benchmarks against Couchbase and other NoSQL products. One of the use cases tested was for caching scenarios in particular, with a common high-volume, key-value

12 workload.

Results shown in Figure 5 demonstrate how strongly Couchbase competes with other NoSQL vendors in multiple clustering scenarios.

Couchbase performs extremely well with the other three workloads in this benchmark as well. See the charts, queries, and explanation of the testing approach that was used in the

Figure 5: Altoros benchmark comparing Couchbase, MongoDB™, and DataStax (Cassandra) performance with a cached key-value lookup and active read/write workload

detailed report at couchbase.com/benchmarks.

Simple migration from Oracle Coherence or Memcached to Couchbase

If you’re looking to replace your existing caching solution – whether Oracle Coherence, Memcached, or another product – the migration to Couchbase Server is a simple process that takes minimal time and effort.

In general, deploying Couchbase Server as a cache is straightforward:

1. Download Couchbase Server

2. Set up your Couchbase cluster

3. Redirect your application to the Couchbase cluster

Drop-in replacement for Memcached: No code changes required

13 Because Couchbase Server is fully compatible with the Memcached protocol, replacing Memcached with Couchbase is very simple. Other than pointing your configuration to the new cluster, no changes to your application code are required. The Couchbase cluster behaves just like a Memcached server and will be automatically discovered by your application. Data will be automatically pushed to the Couchbase nodes.

Migrating from Oracle Coherence to Couchbase Server

Replacing Oracle Coherence with Couchbase Server involves minimal code changes to your application at the cache interaction layer. Because the development effort is fairly straightforward, the process may take anywhere from several days to a couple of weeks. However, once these code changes have been made, the benefits of replacing Coherence with Couchbase – including less complexity, better manageability, easier scalability, and lower costs – are well worth the small effort required.

Beyond caching: Simplify IT infrastructure, reduce costs with Couchbase

Couchbase Server can be a great fit as an affordable, easy-to-manage, high-performance cache. A next step is to consider using Couchbase to replace the primary data store. Since Couchbase Server is a general-purpose NoSQL document database that includes an integrated distributed cache, enterprises can extend their use of Couchbase beyond caching, and deploy Couchbase as the primary underlying database.

In scenarios where a NoSQL database like Couchbase is a good fit for your application requirements, you can significantly reduce costs and simplify your IT infrastructure by consolidating on Couchbase as both cache and primary data store. In fact, many leading enterprises have extended their Couchbase deployment to be the primary data store, across a growing number of solutions including:

Once you have implemented Couchbase Server as a cache – with lower costs, high

• Customer 360/Single account view For use cases like: • Catalog & inventory Management • Customer 360/Single account view • Field service • Catalog & inventory Management • IoT data management • Field service • IoT data management

performance, manageability, and elastic scalability – it may be a good time to consider how to leverage the other benefits of the database, including query, text search, real-time analytics, server-side scripting, and more.

3250 Olcott Street Santa Clara, California 95054

1-650-417-7500 About Couchbase www.couchbase.com Couchbase’s mission is to be the data platform that revolutionizes digital innovation. To make this possible, Couchbase created the world’s first Engagement Database to help deliver ever-richer and ever more personalized customer and employee experiences. Built with the most powerful NoSQL technology, the Couchbase Data Platform was architected on top of an open source foundation for the massively interactive enterprise. Our geo-distributed Engagement Database provides unmatched developer agility 14 and manageability, as well as unparalleled performance at any scale, from any cloud to the edge.