Home / Companies / Tessell / Blog / February 2024

February 2024 Summaries

4 posts from Tessell

Filter
Month: Year:
Post Summaries Back to Blog
PostgreSQL 16 introduces several enhancements, including the load_balance_hosts connection option, which allows applications to distribute connections across multiple target nodes, improving load balancing and avoiding bottlenecks. The require_auth option enhances security by enforcing SASL for non-SSL, SCRAM-SHA-256 authentication modes, and the GENERIC_PLAN option facilitates generating execution plans for queries with parameter placeholders. Additionally, logical replication can now be initiated from a replica node, reducing the load on the primary node, while the new pg_stat_io catalog table tracks I/O requests by each worker process, aiding performance analysis. Other notable improvements include support for ZSTD and LZ4 compression algorithms in logical dumps, new roles for creating subscriptions and utilizing reserved connections, and various flags in VACUUM for managing database statistics efficiently, further solidifying PostgreSQL's position as a leading database management choice.
Feb 20, 2024 3,060 words in the original blog post.
Tessell has announced the formation of a Technical Advisory Board to enhance collaboration and innovation in the database community, inviting members to influence the development of their managed DBaaS platform. The board aims to incorporate community insights to prioritize features and address user needs, offering members exclusive previews of new features and direct communication with the development team. Tessell, a cloud-native DBaaS, is noted for its robust capabilities with AWS and Azure, supporting various database engines including Oracle and MongoDB, and optimizing for performance and economic efficiency through high-performance NVMe storage. The platform's intuitive deployment process and cross-region replication make it suitable for mission-critical databases, freeing developers to focus on innovation and business growth. Tessell has been recognized for its contributions to data management, featured in prominent industry reports and named a GartnerĀ® Cool Vendor.
Feb 14, 2024 473 words in the original blog post.
MySQL Enterprise Edition supports LDAP authentication, allowing the server to authenticate users by accessing directory services like those provided by Microsoft Active Directory (AD). This integration enables the use of consistent user credentials across platforms, enhancing security with AD's password policies. The process involves configuring the MySQL server to communicate with an AD domain controller, installing necessary LDAP client libraries, and employing the LDAP Simple method for compatibility with Microsoft AD. The LDAP server-side plugin, authentication_ldap_simple, is used to facilitate this authentication method, ensuring secure and efficient user management. By creating MySQL users with the same credentials as those in AD, organizations can streamline user authentication and leverage advanced security features within their MySQL infrastructure.
Feb 07, 2024 1,053 words in the original blog post.
Beginning with MySQL 8.0.26, MySQL Enterprise Edition supports Kerberos-based authentication, allowing users to integrate MySQL Server security with existing infrastructure like Microsoft Active Directory or Azure AD. This integration enables the use of existing user names, passwords, and permissions to enhance security through established AD rules. Supporting both MIT (GSSAPI) and Microsoft (SSPI) Kerberos implementations, the feature allows for single sign-on capabilities. The process requires setting up Kerberos Client Libraries on the MySQL Server, enabling the Kerberos Server Side plugin, and mapping MySQL Service Principal Names to Active Directory users. This approach simplifies credential management and leverages advanced security features through MySQL's pluggable authentication system, facilitating seamless integration of AD authentication with MySQL Enterprise Edition hosted on Linux servers.
Feb 01, 2024 1,434 words in the original blog post.