Building a resilient application requires readiness for unexpected database issues, such as temporary network glitches or brief database unavailability, ensuring they don’t affect functionality. In this blog, I’ll demonstrate setting up a solid retry mechanism and manage transactions effectively in a Spring Boot application using YugabyteDB.
Learn to build a scalable AI application with Azure OpenAI Service and YugabyteDB. See how to interface with Azure’s GPT and Embeddings models, embedding storage in YugabyteDB and conducting similarity searches in distributed clusters.
Dive into our step-by-step guide on deploying scalable web applications with YugabyteDB and Azure App Service. Learn how to harness the power of cloud infrastructure, amplify data reliability with YugabyteDB, and bring an eCommerce dashboard to life.
Jay Duraisamy, the SVP of Technology for Data and Analytics at Fiserv, sat down with us to discuss how Fiserv is unlocking the value of their data and providing new services for both merchants and consumers by bringing together data and analytics on one platform.
Tom Eck, Sr. Vice President of Digital Transformation at Fiserv, sat down with us to discuss all things application development, including how Fiserv is planning to monetize their data and how application development teams need to modernize to best support cloud native applications.
Developing distributed, database-backed applications brings a number of performance considerations. Applications are being developed to run across zones and regions, potentially incurring high latency costs if incorrectly tuned. This blog will guide you towards a low latency future by using Node.js Smart Drivers.
To illustrate how to build a geo-distributed application, we will use as an example a Slack-like messaging app. This step-by-step guide starts with the distributed application and API layers, continues on to the distributed SQL database, and finishes with the need/purpose of the global cloud load balancer.
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.
So what is a geo-distributed app? It is generally defined as an app that spans multiple geographic locations for high availability and resiliency. However, Iet’s expand (and then break down) that definition for a better understanding.
This post is an in-depth look at the various techniques that applications needing low latency and high availability can leverage while using a geo-distributed SQL database like YugabyteDB so that the negative impacts of a high-latency, unreliable Wide Area Network (WAN) are minimized.
