Technical Blog


Technical and Product News and Insights from Rackspace

Scaling distributed SQL with ObjectRocket for CockroachDB


Originally published in Aug 2019, at ObjectRocket.com/blog

CockroachDB® is part of the Rackspace ObjectRocket family of database technologies. The scaling abilities of CockroachDB are exciting, with data replication and distribution (maximizing high availability), automatic database rebalancing, and multi-geo data centers supporting data-domiciling compliance, to name a few. And all of this with high data integrity and distributed ACID transactions because the CockroachDB data resiliency is a must-have.

We want to share some of the highlights of scaling with CockroachDB and go over what Rackspace ObjectRocket’s DBaaS offers. As a developer, when you use CockroachDB on our managed-services platform, you can focus on building your applications and not on the intricacies of running a database.

These days, scaling is paramount

Twenty years ago, storage was an expensive concern, and the term Big Data made it clear that we faced big challenges. We had massive amounts of data and no good way to analyze or use that data. But now, technology can handle Big Data and the constant barrage of queries and transactions inherent in our modern world of e-commerce, financial software, research, business administration, and data mining. Another technology frontier, the Internet of Things, increases the number of devices generating data and running transactions online. You can now add cameras, light switches, and refrigerators to the long list of devices that are creating useful data online.

In this landscape, it’s critical to implement a scaling strategy that meets the current demands on your data stores and also allows for the inevitable growth in data and new, not-yet-imagined, sources of even more data and transactions.

Scaling simply means ramping the necessary database resources up (or down) to handle the current workload appropriately. Scale in the following ways:

  • Vertical scaling: Add (or remove) RAM, storage space, and CPU to the underlying nodes within a cluster.
  • Horizontal scaling: Add more nodes when necessary to handle the workload (instead of adding more resources to a single node).

Most relational databases use vertical scaling. However, most distributed databases (often non-relational) use horizontal scaling—which is better for heavy transactional loads, frequent queries, reads/writes, and resiliency requirements. You can scale vertically only so far, because of the technical (computational) limits of a single piece of hardware.

However, scaling horizontally is not constrained computationally and is limited to only the amount of hardware available and what the software supports. What makes CockroachDB unique is that it provides a great solution for horizontally scaling relational databases (traditionally not possible) in response to the rapid, real-time reads and writes that are inherent in distributed online transaction processing (OLTP) systems. You can also scale CockroachDB vertically, but scaling by adding more nodes is the preferred method.

What makes CockroachDB scaling special?

According to Derek Johnson, Product Manager at Rackspace ObjectRocket, the most exciting aspect of CockroachDB’s scaling is how smart it is. After you create and configure the first node, adding subsequent nodes is simplified. In multi-node environments, you can leverage the powerful CockroachDB features of auto-scale, balance data, and self-managed geo-specific compliance requirements to keep your data stores reliable, compliant, and performant. With optimized configurations, you can take advantage of the real powers of CockroachDB. For example, by using the —locality flag to describe the node’s region and availability zone, CockroachDB implements geo-partitioning and automatically keeps data within the specified region.

Here’s a breakdown of some scaling highlights:

Data integrity as your data stores scale

  • Transactions are ACID-compliant, and you can use them in the usual way, by using SQL commands like BEGIN or COMMIT.
  • CockroachDB differs from relational databases. During scaling, it distributes both reads and writes across all relevant nodes instead of all writes going to a single node. This multi-active availability is CockroachDB’s version of high availability and allows geo-spanning.
  • CockroachDB uses consensus replication by sending replication requests to at least three different nodes and then waiting to commit until most of the nodes report back that they have successfully replicated the data.
  • Mediated transactions, with intents and records for each write, prevent transaction conflicts.
  • CockroachDB uses two objects to mediate all transactions: a transaction record and a write intent, which check-in with each other and, if needed, restart the transaction to ensure it commits the latest values.
  • CockroachDB provides a good balance of performance and data integrity due to its data balance and replication.

Geo-partitioning to the rescue!

Instead of creating shards that are then geographically siloed, improving latency but preventing cross-geo queries, CockroachDB uses configuration settings at the range level to replicate data within defined regions. CockroachDB delivers double-purpose value with its unique geo-partitioning capabilities. By configuring the specific region to store data, you achieve both application performance (data closer to users’ applications) and GDPR data domiciling compliance.

The CockroachDB Admin UI has a fantastic geographic display called the Node Map, which shows a map of the world with icons for all nodes and the details for each node. This graphical display helps with planning and troubleshooting latency issues between data stores. When accessing your CockroachDB through the ObjectRocket Mission Control UI, you can link easily to the CockroachDB Admin UI to view the Node Map.

Adding new nodes manually with appropriate configurations allows for smart and rapid scale-outs

  • If you want to spin up new nodes proactively, you can use a command through either the CLI or the Admin UI to create the node and set the needed flags and other configurations.
  • Altough you need to stop and start many databases to scale, with CockroachDB, you can easily add more nodes while the system is under load.

By using orchestration, scaling is handled automatically, with no downtime

CockroachDB offers the following scaling advantages:

  • Scaling CockroachDB through an orchestration platform makes it easy and allows for powerful automation. For example, when you use Kubernetes (as ObjectRocket does), a single command can scale-out CockroachDB, provisioning new resources and spinning up additional pods as needed.
  • Rebalancing data across the nodes happens automatically, even between data centers and different cloud providers.
  • Distributed transactions mean that there’s no impact on workload, no downtime, and no increase in latency.
  • Optimizing server utilization evenly across all nodes is a natural result of CockroachDB’s auto-scaling.

Bringing it all together in a managed service

ObjectRocket offers complete managed services for your CockroachDB data stores by using a Kubernetes container-based architecture. The service includes design and deployment consulting, full technical support, and all of the benefits of the enterprise-licensed version of CockroachDB.

The key features of the managed CockroachDB solution include:

  • Three-node High Availability (HA) clusters
  • Access to the CockroachDB Admin UI though the ObjectRocket UI
  • IP address whitelisting
  • User authentication
  • Transport Layer Security (TLS)

What this means to you is that you get a relational, ACID-compliant data store with a comfortable SQL interface and PostgreSQL wire compatibility, but with automatic HA, easy scalability, and geographic scaling.

ObjectRocket’s managed CockroachDB offering enables you to select the best option for your data needs from pre-defined node types and then horizontally scale by adding as many more of that node type as needed. Our Kubernetes-based platform automatically replaces failed or problematic nodes so we can ensure that your cluster is always up and available.

This is a great time to check out CockroachDB and what Rackspace ObjectRocket provides with our managed services. For some insight into how a managed offering of CockroachDB might solve your data store requirements, read our Top 5 Use Cases blog. Cockroach® has excellent documentation, and if you are interested in having a conversation about CockroachDB or want to learn more, contact us here at Rackspace.

Learn more about Rackspace DBA Services.

Click here to view The Rackspace Cloud Terms of Service.

Use the Feedback tab to make any comments or ask questions. You can also click Sales Chat to chat now and start the conversation.

post avatar
Tana Berry

At ObjectRocket (a Rackspace company), I moved over to the marketing side of the house, learned new magic on how to get out the word about our great DBaaS offerings, and leveraged my previous content and community experience. I focused on creating technical marketing content (mostly blogs) and social media (yay Twitter!), plus doing a bit of work with the dev teams on tech docs. This role took me back full circle to databases, where I started out 20+ years ago. ;-) Rackspace ObjectRocket provides database expertise and management of several popular databases in the Cloud—they do the database work, and enable developers to focus on their application’s product design and coding, not the underlying DB.

Share this information: