Monitoring logs is vital for system performance and issue identification. Splunk offers powerful log management and analytics, enabling comprehensive log analysis. In this blog, we explore exporting YugabyteDB logs to Splunk, providing a step-by-step guide.
Optimize your web testing with parallel Cypress execution using Docker and Jenkins, cutting down test suite time across multiple virtual machines. This guide also covers the integration of Report Portal for detailed reporting and Mochawesome for insightful analysis.
YugabyteDB offers ways to geo-distribute reads. While read replicas are one method, they require more infrastructure. An alternative is to enable follower reads for low-latency access from the primary cluster.
Explore the different data replication options available with YugabyteDB including synchronous, asynchronous, read replicas, xCluster, and change data capture (CDC).
Learn how to integrate YugabyteDB with Amazon Redshift database using the Amazon Web Services(AWS) Managed Kafka Stream (MSK) and YugabyteDB Change Data Capture (CDC) connector.
In YugabyteDB, you can manage the number of shards (tablets) using flags like ysql_num_tablets for total control or ysql_num_shards_per_tserver for control per tserver. Dynamic auto-splitting is also supported for automatic adjustments as data grows.
Yugabyte helps Fortune 500 companies modernize their systems of record, which are integral to the web-based interactions of their customers. These systems require accuracy, consistency, and resiliency. Strategies like replication and sharding help maintain high availability in a cloud native world.
During a massive Texas snowstorm, a power failure affected millions of homes, businesses, and even one of our largest retail customer’s data centers. Despite the widespread chaos, they managed to maintain application availability thanks to YugabyteDB’s geo-distributed cluster, a solution we’ll explore in this blog post.
Distributed SQL offers greater scalability, availability, and geo-distribution of data compared to PostgreSQL, but it is important to understand the differences in behaviors between the two systems in order to make the most of your distributed SQL database.
YugabyteDB uses LSM Tree / SST Files to minimize the risk of data corruption, in contrast to PostgreSQL’s method. This approach, coupled with independent compactions and checksum verification, enhances data integrity.