July 2023 Summaries

The YCQL API supports Time to Live (TTL) functionality, but YSQL does not currently offer this feature. However, database partitions can be used to achieve similar results in a straightforward manner. To implement TTL, you can create a table and partition it based on a date or time column, then detach the partition when a certain period has passed, allowing for automated management once pg_partman support is available.

This summary provides a comprehensive overview of the different error messages and scenarios that can occur when connecting to an Oracle database, including JDBC Thin and OCI drivers. It highlights the importance of troubleshooting complex connection issues and provides guidance on how to resolve them using various methods, such as modifying the tnsnames.ora file, setting environment variables, and using Java KeyStore or the Oracle Wallet. The summary also emphasizes the need for thorough testing and error handling when migrating from Oracle to YugabyteDB with YugabyteDB Voyager.

The best way to handle restart errors in YSQL is to use at least version 2.12 or 2.13 of YugabyteDB with yb_enable_read_committed_isolation=true, which enables the READ COMMITTED isolation level that supports pessimistic locking and reduces the occurrence of restart errors. This isolation level can alleviate all the errors you are running into, especially in cases where there is clock skew between nodes. If upgrading the cluster is not possible, incorporating retries at the application level can also help alleviate the issue.

The Distributed SQL Summit 2023 is now open for registration, set to take place on September 12th. The event aims to bring together the distributed SQL community and industry thought leaders to discuss challenges and opportunities of database modernization and transformation. Attendees will have the opportunity to learn from peers and experts, including Yugabyte co-founder Karthik Ranganathan, who will share new product innovations and the future vision for databases. The summit offers a range of technical demos, presentations, networking, and live discussions, with the goal of enabling modern cloud native applications and transforming organizations into data-driven enterprises.

This paragraph provides a concise summary of securing Spring Boot applications using YugabyteDB and secret manager services. It explains that security plays a crucial role in software development, particularly when managing sensitive data such as API keys, database credentials, and certificates. To safeguard against unauthorized access, it is essential to securely store and access these sensitive data within the application. YugabyteDB offers advanced security features like Transport Layer Security (TLS) encryption, ensuring the protection of Spring Boot applications. Native cloud secret management services like AWS Secrets Manager, GCP Secret Manager, Azure Key Vault, or Hashicorp Vault enable secure storage and management of sensitive data with access restricted to authorized users. The article guides on how to integrate YugabyteDB with these secret manager services to secure Spring Boot applications. It covers enabling encryption in transit for node-to-node communication, enabling one-way TLS for client-to-database communication, enabling mutual TLS for client-to-database communication, and integrating Spring Boot applications with secret manager services like AWS secrets manager, GCP secret manager, Azure key vault, or Hashicorp vault to access sensitive data securely. The article also discusses how to secure the application using mutual TLS, update provider-specific secret manager services, and customize the Hikari datasource by setting root CA, client key, and client certificate properties in the datasource configuration.

If you're using a table in YugabyteDB, the system automatically assigns a key to it, whether user-defined or not. When querying this table, specifying the primary key can significantly improve performance by avoiding a sequential scan of all rows. On the other hand, if the primary key is not specified, YugabyteDB will perform a full scan, which can incur heavy latencies and slow down query execution. To optimize query performance, it's recommended to create a primary key for user-defined tables and consider creating indexes on additional columns or using the INCLUDE *keyword* when necessary.

The YugabyteDB JDBC Smart Driver allows developers to easily manage connections to a distributed system by automatically load balancing across different servers in the cluster when certain nodes or server instances become unavailable. The driver uses Hikari, a high-performance connection pooling framework, to distribute new connection requests and handle connection failures. With the smart driver's connection load balancing feature, developers can configure the pool to prioritize specific regions or zones of the cluster for connection requests, allowing for more targeted and efficient use of resources. Additionally, the driver provides a fallback option that enables connections to be established on nodes in secondary placements when primary nodes become unavailable, ensuring minimal disruption to applications. The YugabyteDB smart driver's ability to seamlessly failover to all or specific servers from the originally connected servers in the cluster makes it an attractive solution for developers looking to improve the reliability and scalability of their distributed systems.

The Pressure Stall Information (PSI) metric in Linux indicates where a database system's workload is being slowed down by CPU, RAM, or I/O. The metric can be accessed through the `/proc/pressure` filesystem and can be queried from SQL using the file_fdw extension in PostgreSQL. To enable PSI, the kernel version must be higher than 4.20, and it must be enabled at boot time. Once enabled, PSI provides valuable information about system bottlenecks, which can help database administrators and developers optimize their systems for better performance. By monitoring PSI metrics such as CPU, I/O, and RAM pressure, users can identify areas of the system that require scaling or optimization to improve overall throughput.

When To Use Range Sharding vs. Hash Sharding` in YugabyteDB is determined by the type of workload and query patterns, with hash sharding being more effective for single-row selection using primary key index, while range sharding is better suited for queries that select a range of rows or when a composite primary key is used. The choice between the two sharding methods depends on the specific use case and can be determined by considering factors such as query patterns, data distribution, and performance requirements. YugabyteDB supports both hash and range sharding, with the ability to specify ascending or descending order for partitioning, allowing developers to choose the most suitable approach for their application.

Yugabyte is now offering its managed database service on Microsoft Azure, expanding its global reach to 15 regions with more to come. This allows users to have flexibility in choosing their cloud provider without vendor lock-in. Dedicated clusters on Azure are governed by the same enterprise-grade SLA as before and maintain a fully-managed experience with convenient upgrades, backups, and monitoring. Deploying these clusters is simple using Yugabyte's web interface or automation tools like Terraform. The integration enhances the user experience and provides more choices for users, making it easier to manage their databases.