March 2022 Summaries

Automation workflows are being used with GitOps and Argo CD for YugabyteDB deployment on Kubernetes. The tutorial explores how to automate YugabyteDB with confidence using all three tools, including single-zone rollout, multi-zone rollout, and Day 2 operations such as cluster upgrades and scaling out/in. GitOps provides a declarative-driven framework that converges the runtime state of services with the desired state defined in Git, while Argo CD follows the GitOps pattern to continuously deliver the application rollout to production. By using Helm chart artifacts, users can roll out database services using Argo CD's "App of Apps" pattern, and override helm parameters for custom deployments.

YugabyteDB is a distributed SQL database that can help companies achieve PCI DSS compliance by enabling the secure storage, processing, and transmission of sensitive payment card data. The platform provides recommendations for achieving compliance with specific requirements, including protecting cardholder data, maintaining vulnerability management programs, implementing strong access control measures, regularly monitoring and testing networks, and maintaining an information security policy. By following these guidelines, companies can ensure they meet the six control objectives set by PCI DSS, which are designed to protect cardholder data security. YugabyteDB has achieved PCI DSS Compliance Level 1 for its fully managed DBaaS offering, demonstrating its commitment to delivering strong performance while maintaining and securing highly sensitive data.

YugabyteDB's pull-based approach to Change Data Capture (CDC) introduced in 2.13 scans changes from the database's write-ahead-log (WAL), utilizing a dependency on the Debezium connector, Apache Kafka as a queue for change updates, and consumer applications that can consume events from a Kafka queue using sink connectors. CDC enables streaming of row-level changes to downstream applications and systems in an efficient manner, with a focus on scalability and fault tolerance, but currently has limitations such as requiring Debezium and Kafka integration and not supporting YCQL tables or system tables. Future releases aim to address these limitations, including the introduction of push-based CDC, connectors for streaming changes directly from YugabyteDB to cloud storage solutions and gRPC-based CDC client APIs.

YugabyteDB 2.13 is a major release that delivers better control over where geo-distributed deployments store and access data, allowing enterprises to lower data transfer costs, improve performance, and ensure compliance with regulatory requirements. The new release includes features such as locality optimized reads, improved backup and recovery capabilities, and enhanced security and compliance features. Additionally, YugabyteDB 2.13 provides a more developer-friendly experience with the introduction of Cloud Shell, CDC, simplified application deployment, and new developer tools like MyBatis and Dapper ORM support. The release also includes several planned features for upcoming releases, including database-level multi-tenancy, faster bulk-data loading, and support for pessimistic locking.

ybio is a PL/pgSQL-based load generator for PostgreSQL and YSQL, specifically designed for flexible IO testing in YugabyteDB. It can perform various types of stress tests on specific parts of the database infrastructure without requiring client installation. ybio differs from other benchmark tools like pgbench, focusing solely on stress testing the database server side rather than simulating application execution patterns. The tool is highly customizable with a range of configuration options that allow users to test different aspects of their database, such as primary key settings, index types, and tablet configurations. By leveraging its PL/pgSQL-based architecture and running inside YSQL, ybio can stress the database maximally without being bound by client tool network limits. This allows for a wide range of tests to be performed on various parts of the database, including selectivity, update, delete, and insert operations, making it an ideal tool for database administrators and developers looking to optimize their YugabyteDB performance.

Lakshmi, a final year student at NUS Business School, joined the Yugabyte Asia Pacific Japan (APJ) team as a tech product marketing intern. She had previously gained experience working with startups and government institutions, including education, construction, and corporate communications. Lakshmi was drawn to Yugabyte APJ due to its diverse team, open-source software, and startup-like environment, which allows her to innovate and take on new challenges. The company's rapid expansion and emphasis on adaptability also attracted her. With her background in business analytics and marketing, Lakshmi is excited to contribute to the team's strategic direction and learn more about the Yugabyte product and its applications.

YugabyteDB is a 100% open source, distributed SQL database system that utilizes a two-layer architecture to achieve its goals. This architecture consists of an extensible query processing layer and a distributed document store, which provides strong consistency with global secondary indexes. The query processing layer, referred to as YSQL, allows for stateless processing without the constraints of synchronizing states and caches across multiple nodes. This statelessness enables complex features that are only possible with this architecture, including support for complex SQL features such as multi-row and multi-table operations. YugabyteDB's two-layer architecture is compared favorably to other databases, including Oracle RAC and Amazon Aurora, which have limitations in terms of scalability and availability. Additionally, YugabyteDB's query processing layer reuses PostgreSQL, allowing access to its feature-rich ecosystem while maintaining a stateless design that enables true scale-out capabilities. The distributed document store, or DocDB, distributes data across multiple servers and allows for fully consistent cross-node transactions, providing strong consistency with global secondary indexes. This architecture also provides logical replication, which is simpler and more autonomous than traditional physical replication methods, allowing for greater agility in the cloud-native environment. Overall, YugabyteDB's two-layer architecture represents a significant innovation in distributed SQL databases, enabling true scale-out capabilities while maintaining strong consistency and availability.