YugabyteDB’s rich deployment and replication options are a must for any developer or technologist building a modern, distributed cloud application. In geo-distributed environments, performance, developer convenience, and compliance are key requirements that organizations must design in their data layer – to avoid the trap of assuming that they will magically exist simply because an application is located in the cloud.
YugabyteDB 2.13 is the latest version, providing better control over where data is stored and accessed, a key feature of modern applications in a geo-distributed environment. Built-in capabilities allow businesses to reduce data transmission costs, improve productivity and ensure regulatory compliance. The latest version of YugabyteDB expands the capabilities of geo-allocation of the database by adding new features that improve performance, increase control over archiving and intelligently use local data for reading.
Today, YugabyteDB’s distributed SQL database helps thousands of developers speed up cloud flexibility, reduce costs, and reduce risks without locking up the provider. This allows them to focus on business growth and spend less time managing complex data infrastructure. Let’s take a look at nine key features in the latest version of YugabyteDB.
Regional local data and cloud archiving
YugabyteDB disseminates and stores data within geographic regions to help organizations with data domicile regulations such as the GDPR in Europe. We expect additional legal jurisdictions to adopt similar laws next year. This means that modern database management systems must provide simple, natural functionality to help organizations meet new and updated compliance requirements.
YugabyteDB 2.13 allows organizations to control where database backups are located by explicitly limiting them to specific geographic regions. Based on the location of the data defined at the time the table was created, each TServer saves files only to the backup destination that corresponds to the configured region.
In addition to meeting these data domicile requirements, storing data in cloud regions reduces the cost of cloud data transfer by avoiding interregional data copying.
Better performance for regional-local transactions
The “Transaction Status” table follows status of transactions. Under the covers, this table is just another broken table in the system. However, it does not use RocksDB, instead it stores all its data in memory supported by Raft WAL.
To achieve A (atomicity) c ACID transactions, along with data operations, we also make atomic changes in the state of transactions. Because this transaction status table is stored as global, it can become a barrier to geo-split transactions.
In YugabyteDB 2.13, the global transaction status table is optimized for access from different regions. Because the transaction status table is also geographically separated, it eliminates the need for a two-way trip to remote regions and reduces request delays by keeping relevant metadata close to users.
YugabyteDB automatically creates a transaction status table using the user’s table location information. However, you can also create a transaction status table manually. To do this, use create transaction status command followed by modify_table_placement_infoto set the location information for the newly created transaction status table.
The materialized view is a pre-calculated set of data extracted from a request specification and stored for later use.
Because the data is pre-calculated, directly requesting a materialized view is faster than executing a query to the main view table. Materialized views can also significantly improve the productivity of workloads, which are characterized by common and repetitive requests.
With YugabyteDB 2.13, materialized views are recalculated in the background when the base tables change. Therefore, any additional changes to the data from the base tables are automatically added to the materialized views. Materialized views return new data, but if changes to the base tables can invalidate the materialized view, the data is read directly from the base tables. If the changes to the base tables do not undo the materialized view, then the rest of the data is read from the materialized view and only the changes are read from the base tables.
TPC-C performance update
For those new to TPC-C, this is an OLTP system benchmarking tool used to measure performance when processing transactions generated by an OLTP application in the real world. He models a business that has a warehouse, multiple areas and inventory for these warehouses, as well as items and orders for these items.
Of course, the number of warehouses is the main configurable parameter that determines the scale of implementation of the benchmark. Increasing the number of warehouses increases the size of the data set, the number of concurrent customers, and the number of concurrent transactions.
With YugabyteDB 2.13, the database can scale up to 1.27 million tpmC with 150,000 warehouses, resulting in an efficiency score of 99.29%.
Change Data Collection (CDC)
Change Data Collection (CDC), introduced in YugabyteDB 2.13, allows many downstream applications and services to consume a continuous and endless stream of changes to Yugabyte’s databases. Streams are scaled to each YugabyteDB cluster, regardless of its size. They also have the least possible impact on production traffic.
The types of changes in the data captured include all changes in the rows (ie insertions, updates, deletions). The CDC also covers changes to metadata, such as creating, modifying, or removing database objects, columns, and tables using DDL.
Every CDC event is completely self-describing. This means that the event key and value contain a payload with actual information, a schema that fully describes the structure of the information, and cluster source information.
How does the CDC provide sequence semantics? Here is how it is implemented in YugabyteDB 2.13:
- Delivery guarantee for ordered tablet: All row changes in the same tablet process in the order in which they occurred.
- At least one-time delivery: In the event of failures that result in the loss of a message or that take too long to recover, the messages are retransmitted to ensure delivery at least once.
- There are no gaps in the flow of change: There is always a guarantee that receiving any change means that all older changes have been received in one line.
Simplified application implementation
With YugabyteDB 2.13, developers have access to fully automated and integrated cloud development workflows. These workflows can be pre-configured with YugabyteDB using cloud development environments, such as Gitpod and GitHub Codespaces. Both GitHub Codespaces and Gitpod workspaces can provide an immediate development environment with a pre-configured YugabyteDB cluster.
New tools for developers
YugabyteDB 2.13 provides support for MyBatis and Dapper ORM (Object-Relational Mapping) tools. This allows developers to use new .NET and Java constancy frameworks to simplify building YugabyteDB applications.
- MyBatis: MyBatis is a premium constancy framework with support for custom SQL, stored procedures, and advanced mappings. MyBatis eliminates almost all JDBC code and manually setting parameters and retrieving results.
- Duper: Dapper is an object-relational mapping product for the Microsoft .NET platform. It provides a framework for comparing an object-oriented domain model to a traditional relational database. Its purpose is to free the developer from a significant part of the program tasks related to the constancy of relational data.
Compliance with SOC 2 type 1
Yugabyte has successfully completed the System and Organizational Control (SOC) Exam 2 in accordance with the American Institute of Certified Public Accountants (AICPA) Credentials for Security, Availability, Processing Integrity, Confidentiality and Confidentiality.
In particular, this accreditation confirms Yugabyte’s commitment to provide detailed information and assurance on security controls, as they are linked to our SaaS system.
YugabyteDB 2.13 includes improved security and improved management capabilities built through Yugabyte’s deep partnerships. These new partnerships include:
- HashiCorp Vault: Use preferably by industry Hashicorp Vault with YugabyteDB enjoy a centralized, cloud-independent key management system (KMS) with secure access to secrets.
- Imperva Cloud data protection: Use ready-made support to simplify the monitoring and tracking of data in YugabyteDB for audits and vulnerability detection.
YugabyteDB for geo-distributed workloads
Yugabyte’s mission is to provide the most user-friendly distributed SQL database. The release of YugabyteDB 2.13 now allows simplified coding by unloading and automating key features in the data layer. It enhances the developer experience by providing easy, interactive learning and greater access to preferred developer tools.
Many of the world’s largest Fortune 500 companies, including Kroger and General Motors, use YugabyteDB for database upgrades, cloud-based applications, and geo-distributed workloads. The enhancements introduced in YugabyteDB 2.13 allow the database to deliver critical business results faster, while responding more quickly to external and internal changes. YugabyteDB helps organizations become truly data-driven by eliminating trade-offs found in legacy databases. This means that organizations can instead prioritize innovation and an improved customer experience.
Karthik Ranganathan is the co-founder and technical director of Yugabyte, the company behind YugabyteDB, a transactionally distributed SQL database for cloud applications. Ranganathan received a bachelor’s and master’s degree in CS from IIT-M and UT Austin. Ranganathan was one of Facebook’s original database engineers, responsible for building distributed databases such as Cassandra and HBase. He is the creator of Apache HBase and was an early contributor to Cassandra before being provided with open source by Facebook.
The New Tech Forum provides a place to explore and discuss emerging corporate technologies in unprecedented depth and breadth. The choice is subjective, based on our choice of technologies that we consider important and of greatest interest to InfoWorld readers. InfoWorld does not accept marketing guarantees for publication and reserves the right to edit all content provided. Send all inquiries to email@example.com.
Copyright © 2022 IDG Communications, Inc.