What exactly do we mean when we talk about use cases? At a high level, a use case is a ”job to be done” for which software is a part of the solution to a problem for a particular business unit.
Within a company/business unit, there will be different teams, each with their own set of use cases to address. A single use case can serve multiple business functions, and may share the same service with other use cases (1-to-many or many-to-many).
For example, this diagram takes a hypothetical retail goods company and details what they might need in terms of software solutions to run the business. You can see that the same use case can apply to multiple business units, and each use case is made up of several applications and workloads.
It’s worth noting that organizations often classify use cases differently – and that’s okay! At the end of the day, use case interactions power businesses and enable them to deliver on their promises to customers.
What use cases are a fit for CockroachDB?
If you’ve paid a bill online, ordered an item from your favorite ecommerce site, or navigated a series of security steps to verify your identity, then you’ve interacted with the types of services powered by CockroachDB.
At Cockroach Labs, we’ve worked with thousands of customers who are architecting mission-critical use cases on CockroachDB so that they can future-proof their infrastructure and deliver new and exciting experiences for their customers.
In our new guide, we discuss 12 common use cases for CockroachDB and dive deeper into the four most popular use cases: User accounts and metadata, identity access management, payments, and order and inventory management. These use cases span all different types of verticals, so the guide is organized into three buckets: use cases serving People, Money, and Things.
Here’s a preview of what you'll find in the guide...
People power products and services
People, or rather, customers, are what power the economy and can make or break a company’s success. The actions customers take within a particular application or with a service directly impact performance and can test the limits of the software’s infrastructure.
In order to meet customer expectations, organizations require a resilient underlying infrastructure that can effortlessly scale and serve people regardless of their location. In this section we cover the following CockroachDB use cases: User accounts and metadata, identity access management, and gaming.
Money makes the world go round
Aside from fintechs, banks, and various financial institutions, other industries rely on the management of people’s money – from retailers with POS systems, to sports betting apps with real-money gaming, to logistics companies that need to bill their customers.
People might make or break a company’s success, but money makes the world go round. The movement of money naturally generates heavy transactional workloads which requires the right underlying foundation. In this section we cover the following CockroachDB use cases: payments, banking and wallet, trading, and betting.
Things have a mind of their own
Like people and money, businesses have many “things” that need to be managed, tracked, and stored. Some of these use cases have been around for decades – railroad routing systems, factory order management, shipping logistics – and are taking a new shape to fit into the modern era.
Others have emerged more recently to keep pace with the increased volume of internet-connected devices and machine intelligence. In this section we cover the following CockroachDB use cases: order and inventory management, routing and logistics, IoT and device management, digital storage management, and AI/ML feature store.
Dive deeper into CockroachDB use cases
Global enterprises rely on CockroachDB to drive business growth and meet customer expectations. This guide includes real-world customer examples and reference architectures to help you see how your use case might be a fit for CockroachDB.
