What is Cloud Database? Definition & FAQs | ScyllaDB

Cloud Database

Cloud Database Definition

The term cloud database or cloud-based database could refer to either:

This page focuses on database-as-a service offerings.

Cloud Database FAQs

What Are Cloud Databases?

Traditionally databases were installed in on-premises environments. But with the advent of the public cloud, many of these traditional databases simply underwent a “lift-and-shift” to public cloud servers. They were not significantly rearchitected to take advantage of the cloud. They were merely deployed there instead. Cloud databases could be deployed to private, public, hybrid cloud or multi-cloud environments. Today, the term cloud database usually refers to a database offered via the database-as-a-service model.

Database as a Service (DBaaS)

The database as a service (DBaaS) model allows organizations to deploy and access a database without worrying about hardware purchase/setup, database installation and configuration, or database maintenance and administration. The database runs on the service provider’s cloud infrastructure (or the user’s own cloud infrastructure) and the service provider offers administrative, database management, maintenance, and operational tasks to the end-user.

DBaaS offerings generally provide automation for backup and restores, health and high availability monitoring, patching and upgrading, provisioning, scaling, and security. By optimizing and outsourcing infrastructure management, the DBaaS model enables development teams to focus on their applications and leave database management to the vendor, who provides expert 24/7 services and support.

A cloud database-as-a-service can offer advantages such as:

Most DBaaS offerings are available across public cloud market leaders Amazon Web Services (AWS), Google Cloud, and Microsoft Azure, as well as many private cloud providers.

According to the latest Gartner Magic Quadrant for Cloud Database Management Systems report, the largest DBaaS vendors include:

Other notable DBaaS offerings include…

SQL cloud databases:

NoSQL cloud databases:

What you are responsible for with a cloud-hosted self-managed database (left) versus with a database-as-a-service (right).

What Parts of Cloud Database Management Are Covered by the Service Provider?

One of the greatest advantages of a fully-managed cloud database service is that it relieves teams from the time and hassle of dealing with their database, enabling them to focus on their product.

Advantages and Disadvantages of Cloud Databases

To identify the best cloud database solution for your team, consider these cloud database advantages and disadvantages:

Benefits of Cloud Databases

The best cloud databases offer benefits such as:

Flexibility A cloud database enables your team to get started fast and evolve as your projects grow. You can choose an option that fits your current workload and purchasing preferences, then seamlessly evolve it over time. You can select from a range of servers as well as monthly or annual pricing options. You can start small with a cluster for development and then increase the size of the cluster for full-scale testing and QA, and then even further as you scale to meet your production deployment requirements.

Expert database management A primary benefit of using a cloud database is that a team of experts from the DBaaS vendor manage your cluster. The DBaaS vendor will perform monitoring, backup, restore, node repairs, cluster resize operations, nodes management, apply hotfixes and upgrades. You are only responsible for managing your application and application-specific database requirements such as schema design, database sizing, infrastructure selection, and capacity planning.

Reduced hassle and overhead With a cloud database, your team does not need to develop or hire specialized resources, such as database administrators, DevOps, and security personnel to manage the database. You also don’t need to select hardware, purchase it, wait for it to arrive, install it, or set it up, or maintain it, thus saving on hardware datacenter techs.

Security All of the best cloud database vendors make significant investments in security. Most cloud based database solution vendors have a far more secure way to protect sensitive data than an in-house team. This might include single-tenant hardened security, encrypted backups, key management, hot fixes for the latest security updates, as well as Virtual Private Cloud (VPC) peering.

Disaster Recovery Distributed cloud databases usually replicate your data across multiple availability zones within a region so there’s no single point of failure. They also allow you to more replicas and expand your cluster to multiple data centers, as you wish. Centralized cloud based databases secure data through remote server backups in the event of an equipment failure, a natural disaster, or a power outage.

Common Database Challenges in the Cloud

Cost at Scale The most commonly cited challenge of DBaaS cloud databases is cost at scale.

No matter where you are today, it’s important to anticipate future growth and plan how you can cost-effectively scale your applications to support business growth without causing an exponential increase in costs.

Most cloud database pricing models are based on operations per second, storage, and actual traffic in the cluster. Items such as secondary indexes, if available at all, come at a premium. If you need fast reads, you need to deploy dedicated hardware to support these reads from a specialized cache, which is usually sold at a premium by the DBaaS vendor If your application needs to serve multiple geographical regions, the replication comes at a premium If you scale beyond certain workload, the DBaaS vendor might start to limit your available capacity in certain regions or charge you a premium for having high load on certain regions.

Many database solutions charge you per write and read units. While these initial charges might seem small in comparison to your storage costs, storage costs are actually the least costly part of the system. For example, assume that one read unit will cost you one-millionth of a cent. When your customer base grows to 10,000 active users per second — each reading one block per second — a year of just those reads will cost you over $3,200 (and that’s for only the 10,000 operations per second that occur on that specific cluster). What happens if your user application requires more than one block of reads per second? At that point, just start multiplying those thousands of dollars every time. These read and write operations can become quite expensive over time.

Vendor Lockin Another common cloud database challenge is vendor lock-in. Make sure you’re not dependent on a cloud database solution that prevents you from easily migrating when your needs change or you decide it’s time for a different approach. Consider the ability to change cloud platform providers as well as database service providers — or even to move from a cloud to on-premises deployment (a process known as cloud repatriation). You might also consider running across multiple public clouds (known as multi-cloud deployments) or span your workload on both public cloud and on-premises deployments (known as hybrid cloud). If these options are important to you, investigate whether you can migrate without changing your application or increasing your total cost of ownership.

Unacceptable Limits If you have large partitions, huge payloads, multi-terabytes or petabytes of data, you should ensure that a potential cloud database solution will not limit you to a narrow scope of workload or payloads.

Different cloud database services have different read and write characteristics and capabilities. Some even limit the size of your data items or the total storage you’re allowed. Can your application work effectively within those boundaries?

Ensure that your database solution provides operational continuity and scale under the extreme throughput, latency, and storage requirements that you’ll see as your application grows and grows.

Latency With users now expecting instantaneous experiences — all the time — the performance of your database is critical. If response speeds matter for your business, look for a cloud database that can consistently deliver low-single-digit millisecond latencies. Check benchmarks, user experiences, Jepsen test shakedowns, and so forth.

Selecting a database that provides reliable latency guarantees under the maximum throughput load is especially critical when your business is experiencing record-high transactions and activity. So is making throughput and latency metrics available to your operations team. These metrics will help you perform accurate capacity planning… and plan for future growth as well.

Downtime Teams often move to a cloud database solution to guarantee business continuity. Organizations want to ensure zero downtime and rest assured that customers and users can reliably interact with the application 24/7, 365 days a year. To ensure this, look for a database that’s purpose-built for high availability and disaster recovery.

Cloud database solutions that use a peer-to-peer architecture have high resiliency because there’s no single point of failure that can bring down the cluster. A peer-to-peer architecture helps even out the workload on the different servers that are deployed underneath the database solution — without creating bottlenecks or requiring a complex and expensive load balancing system to ensure that the load is well distributed and failover is smooth and fast.

Select a solution that delivers built-in resiliency, a solution that does not force you to purchase premium auxiliary products just for the simple task of having high availability, some type of a connection between the different data centers, and so on. These extra costs can add up fast.

Limited Ecosystem Look for a cloud database with a complete ecosystem behind it. This involves support for your preferred programming environment as well as your complete data ecosystem. If you need to build one-off solutions to satisfy your specific use cases, that’s going to drain your resources and inhibit agility as your needs evolve and the ecosystem advances.

First, review all of your application’s data ingress and egress requirements and select a cloud database solution that supports well-known and established solutions for these data pipelines ( Kafka, Spark, Pulsar, Redpanda, etc.). This will result in significant productivity gains and cost savings down the road.

Second, ensure there’s native support for your programming environment. Check if your database service provider publishes a performant, reliable, actively-maintained driver for your specific application languages; this will increase both the client and the DBaaS efficiency.

Cloud Database vs Traditional Database

How do cloud databases compare to traditional databases?

Cloud databases and traditional databases (e.g., on-prem self-managed databases) differ significantly in terms of deployment, scalability, maintenance, and accessibility.

Traditional databases offer more control, but are usually costlier and more time-consuming to manage.

Organizations typically host and manage all aspects of traditional databases onsite. This includes procuring and installing hardware, configuring and maintaining the database, and ensuring data security.

In contrast, third-party service providers host cloud databases. Compared to traditional databases, they offer greater scalability and accessibility, and reduced operational overhead and costs.

There are also combined approaches. By hosting databases using Infrastructure-as-a-Service (IaaS) or self-managing them on a cloud-based platform, organizations retain some control but can still achieve scale.

What are the types of databases in the cloud? Is there a hybrid option that bridges the cloud database vs traditional database management systems?

Hybrid cloud databases. These are deployed across data centers and cloud environments to synchronize data for workload mobility and disaster recovery.

Multi-cloud databases. Some organizations deploy databases across multiple providers to avoid cloud vendor lock-in and access unique features on different platforms. Multi-cloud databases also enable data replication and synchronization across cloud environments.

Cloud databases vs traditional databases: differences, advantages, and disadvantages

The main differences between cloud databases vs traditional databases lie in their deployment model, scalability, management, accessibility, and cost structure.

Advantages cloud databases offer include:

Disadvantages of cloud computing include:

Advantages of traditional database management systems:

Disadvantages of traditional databases:

How do cloud databases vs traditional databases manage security and data control?

Both types of databases implement security measures to protect data. Cloud databases often provide additional built-in security features and compliance certifications. Traditional databases are reliant on the organization which must manage all aspects of security and compliance internally.

How does topology and data distribution differ between a cloud database vs traditional database?

Cloud database architecture distributes data across multiple servers or nodes, often via geographically dispersed data centers. They also handle requests in parallel using technologies such as sharding and replication.

Traditional database management systems run all components on a single server or a tightly coupled cluster. This monolithic deployment is typically located on-premises or in a private data center.

How do cloud databases vs traditional databases differ in terms of cost, seed investment, and device dependence?

Cost

Cloud databases generally use pay-as-you-go pricing models with annual discounts available for longer term commitments. Traditional databases involve significant upfront costs to cover procuring hardware, setting up infrastructure, and buying software licenses, as well as ongoing maintenance and management.

However, the long-term operating costs of each type of database depend on utilization rates, depreciation schedules, and maintenance expenses.

Seed investment

The minimal upfront investment cloud databases require make them attractive for startups and small businesses with limited capital or resources that need to quickly prototype, develop, and launch applications without the need for significant infrastructure investment.

Device dependence

Cloud databases offer access and data management through web-based interfaces, APIs, or client applications, enabling remote work, collaboration, and data sharing across devices.

What are top use cases for cloud-native databases vs traditional databases?

Cloud-native databases are well-suited for various use cases:

Does ScyllaDB Offer a Cloud Database?

ScyllaDB is a NoSQL database built with a close-to-the-hardware, shared-nothing approach that optimizes raw performance, fully utilizes modern multi-core servers, and minimizes the overhead to DevOps. ScyllaDB is API-compatible with both Apache Cassandra and the Amazon DynamoDB cloud database, yet is much faster, more consistent, and with a lower TCO.

Many leading teams are building real-time applications that run at global scale with ScyllaDB Cloud, which is a fully managed NoSQL DBaaS.

Why do users consider ScyllaDB Cloud as the best NoSQL cloud database? Because ScyllaDB Cloud is a fully-managed NoSQL database that provides performance at scale as a highly affordable Database as a Service (DBaaS). It’s available on AWS, Google Cloud, and, using technologies such as Google Anthos or RedHat OpenShift, can be deployed in multi-cloud environments. With ScyllaDB experts managing your database, your team is spared from performing database administrative tasks such as automatic backups, repairs, monitoring, performance optimization, and security hardening. ScyllaDB also provides 24×7 maintenance and support, and we offer database migration services to jumpstart the process.