Home / Companies / Yugabyte / Blog / February 2024

February 2024 Summaries

7 posts from Yugabyte

Filter
Month: Year:
Post Summaries Back to Blog
YugabyteDB is a distributed SQL database that delivers built-in resilience to protect against data loss and app disruption. However, Tier 0 applications need extra protection from human error, data corruption, and unexpected scenarios. This is where Commvault Cloud comes in, providing an added layer of protection through enhanced integration between the two platforms. The combined solution enables comprehensive protection, automated healing, granular control, centralized management, long-term retention, and ultimate security for organizations using YugabyteDB. To get started, customers can configure a YugabyteDB cluster directly from the Commvault Cloud console, following nine steps that include adding a cluster, configuring an access node, selecting a plan, and more.
Feb 29, 2024 646 words in the original blog post.
A retry mechanism is essential for modern software systems, enabling them to quickly recover from transient errors or network outages by automatically retrying failed operations. In a Spring Boot application with YugabyteDB as the database, setting up a robust retry mechanism involves understanding configuration, crafting retry policies, integrating these policies into the application, and utilizing a retry interceptor to manage transactions effectively. The goal is to ensure that temporary issues don't result in failed operations but are gracefully handled by pausing and retrying. By using a retry policy with exponential backoff, an application can minimize latency while maximizing the chances of successful transactions, ensuring a smooth user experience despite transient errors or network disruptions.
Feb 27, 2024 2,036 words in the original blog post.
Amit Chauhan's guide on designing a retry mechanism for resilient Spring Boot applications with YugabyteDB emphasizes the importance of handling transient errors, such as temporary network glitches, to maintain application functionality. The guide outlines setting up a robust retry system and managing transactions effectively, likening the process to a coffee shop smoothly handling supply disruptions. It details configuring retry properties, crafting retry policies using PostgreSQL error codes, and integrating these policies into the application. Different transaction management strategies are discussed, including using annotations, templates, and direct transaction management, allowing for flexibility and precision in handling database operations. The guide also includes a practical demonstration using a sample application to simulate retry mechanisms and manage transactions, underscoring the need for adaptable and reliable systems in modern software development.
Feb 27, 2024 2,121 words in the original blog post.
YugabyteDB Aeon now supports more identity providers such as PingOne and Okta for single sign-on (SSO), giving users flexibility to choose their preferred authentication method, automating user setup without manual invitations, and simplifying login processes. This update enhances security, convenience, and scalability, offering a unique blend of security through centralized management, robust multi-factor authentication, and seamless no-code orchestration. Organizations can meet industry standards and regulations for identity and access management, reduce IT costs associated with password resets, and improve productivity for their users.
Feb 22, 2024 451 words in the original blog post.
Paramount+ successfully transitioning to a multi-region architecture demonstrates the importance of choosing the right database and design patterns for achieving low latency, scalability, and resilience across multiple cloud regions. The company's use of YugabyteDB and its distributed SQL database architecture enabled them to tolerate region-level outages, scale their streaming platform to accommodate millions of users during peak periods, and maintain low latency across distant locations. By implementing a multi-region setup correctly, developers can build applications that are similarly resilient and performant, even in the face of complex scalability challenges.
Feb 20, 2024 2,390 words in the original blog post.
Paramount+ has shattered records in the NFL season with its live stream, including the most-watched AFC Championship Game ever and an audience of 50+ million viewers during two consecutive NFL weekends. To support such massive viewership levels, Paramount+ designed a system that is fundamentally scalable, robust, and resilient, leveraging YugabyteDB to provide database scale, performance, and availability. The use of horizontal scaling, multi-region architecture with data locality, and PostgreSQL compatibility enabled the system to handle huge spikes in viewer traffic during the Super Bowl without downtime or data loss, providing exceptional user experience.
Feb 11, 2024 1,115 words in the original blog post.
The integration of YugabyteDB with Apache Hudi enhances data lakehouse capabilities through real-time data processing, efficient upserts and deletes, and improved consistency and scalability. This synergy is especially beneficial when both transactional integrity and efficient data lake operations are needed. The combination provides benefits such as enhanced data processing, scalable and fault-tolerant architecture, strong consistency and ACID compliance, optimized data pipelines, advanced data recovery and replication, accelerated query performance, and unified data governance. Apache Hudi's integration with YugabyteDB enables real-time CDC for analytics, incremental data loading/ETL using HoodieStreamer, and efficient ETL pipelines. The integration is particularly advantageous for applications requiring real-time processing, transactional consistency, and handling large amounts of data in distributed environments. The synergy between Hudi's incremental data processing and YugabyteDB's distributed SQL capabilities offers a compelling solution for modern, data-intensive applications.
Feb 06, 2024 4,140 words in the original blog post.