A US-based bank revamped its data platform to meet the demands of the digital banking era and the need for real-time customer interactions. Central to their efforts was a unified data platform, capable of handling trillions of reads and writes while ensuring high availability and low latency, catering to diverse query patterns.
In an earlier blog, we broke down the definition of geo-distributed apps. So now let’s compare and contrast geo-distributed apps those apps that are deployed within a single data center or availability zone. A good way to make this comparison to understand the differences and find the similarities is to drill down into the architecture.
As you make progress with your infrastructure and application modernization efforts, it’s essential that you also update and invest in your cloud native data layer.
This blog discusses the newly released YugabyteDB on Tanzu Reference Architecture paper.
This blog post explores the most popular multi-region database deployment options by designing a data layer for a Slack-like corporate messenger.
In this short blog post we are going to give you a quick overview of the components that make up a YugabyteDB universe.
YugabyteDB is composed of nodes. We collectively refer to this collection of all nodes as a universe. These nodes can be physical machines, virtual machines or containers (e.g. Kubernetes).
A YugabyteDB universe is made up of one or more clusters. At a minimum it will contain a primary cluster,