October 2023 Summaries

You can now automatically trigger HTTP callbacks on events in PlanetScale to build custom integrations, notifications, and workflows. Webhooks allow you to get near real-time data through automation, pushing information when an event occurs instead of polling external services. This feature makes the PlanetScale database platform extendable and easy to customize for your workflows. With webhooks, you can create notifications in various tools, integrate with CI/CD processes, and update external issue trackers. PlanetScale offers a range of events that can trigger webhooks, including branch creation and deploy request status updates. Webhooks are currently in beta and invite users to share feedback and suggestions for future integrations.

MySQL replication is a process that synchronizes multiple MySQL servers to keep them in sync. It allows for improved performance and scalability by distributing workload across multiple servers. This can be achieved through various use cases such as read-only connections, backups, analytical workloads, high availability, and planned upgrades. By configuring replicas of the database, changes made to the primary server are also replicated to the replicas, ensuring that data remains consistent across all servers. This approach enables better performance, reduces downtime, and simplifies maintenance tasks.

To sync user data from Clerk to a PlanetScale MySQL database using webhooks and Netlify, start by setting up a PlanetScale database and a Clerk application. Then, fork the orbytal.ink project on GitHub, deploy it to Netlify, and configure environment variables for the database connection and Clerk API keys. Next, create a Netlify Function that will act as an endpoint to receive messages from Clerk, parse the incoming event body into a ClerkWebhook object, and update or insert data into the PlanetScale database accordingly. Finally, test the function by creating an account in Clerk and verifying that the user's information is synced with the PlanetScale database, which can then be accessed directly in your application. This setup allows you to utilize Clerk for authentication and user management while still having access to users' information in your own database.

PlanetScale Managed is a single-tenancy deployment option for AWS and GCP users, offering a fully managed database solution with benefits including private database connectivity, sharding, HIPAA compliance options, PCI compliance, additional support options, and deployment to multiple regions. PlanetScale Managed is available as a packaged data plane on Vitess and Kubernetes, deployed to an owned sub-account, allowing users to interact with their databases through the same API and web interface as the hosted product.

Introducing database reports Bringing weekly reports of the most important parts of your database, straight to your inbox, PlanetScale is introducing a new feature that provides curated database reports delivered weekly to users' inboxes. These reports will initially include slow database queries and deploy requests, as well as a summary of database storage changes, providing users with actionable insights into their database performance and activity. Users can easily unsubscribe from these reports if needed, and PlanetScale plans to continue iterating and adding new features based on user feedback and needs.

A well-architected caching system can help reduce the load on MySQL databases and increase application performance, but it also introduces setup complexities and potential issues such as inconsistent data and thundering herd problems. Caching systems like Redis and memcache are popular distributed caching solutions that can be used to improve application performance by reducing the number of database queries. When implementing caching with MySQL, it's essential to consider data consistency and cache expiration strategies to mitigate these issues. Additionally, a caching system like PlanetScale Boost can simplify the process of adding caching to an application by living within the existing Vitess database cluster.

MySQL partitioning is a technique used to split large data into smaller chunks, improving performance and reducing storage needs. It involves dividing a table into partitions based on specific criteria, such as numerical ranges or fixed values, allowing for more efficient querying and maintenance operations. Partitioning provides benefits like faster query performance, reduced storage requirements, and simplified maintenance tasks, but it also has drawbacks, including limitations on data types and the need to properly understand access patterns. MySQL partitioning is a native feature of MySQL and can be used in conjunction with other scaling strategies, such as sharding, which involves splitting tables across multiple servers. While partitioning is not supported in PlanetScale due to its focus on horizontal scalability, it remains an important technique for improving database performance.

The text discusses the intricacies of MySQL's connection handling mechanisms, focusing on how to optimize connection pooling and enhance concurrency. This deep dive into MySQL's architecture aims to provide a comprehensive understanding of its inner workings for improved performance.

We utilized Markdoc to create a custom, extendable product onboarding at PlanetScale, aiming to provide a one-track path for developers to connect and query their databases regardless of the language or framework used. We leveraged Markdoc's Markdown-based syntax to build an interactive and personalized content experience, incorporating variables to customize user credentials and adding custom nodes to render code snippets with file attributes. This allowed us to extend the code blocks with additional functionality, such as detecting the user's operating system and selecting a certificate for secure connections. The outcome of using Markdoc has been positive, making maintenance and updates manageable, and we are excited to share our onboarding process with others who use Markdoc.

PlanetScale and Amazon RDS are both managed MySQL database services with different architectures and features. PlanetScale is built on open-source Vitess technology, offering horizontal sharding, Git-like schema change workflows, automatic backup, recovery, advanced query analytics, and multi-region replication capabilities. It can be deployed on multiple cloud platforms like AWS and GCP. Amazon RDS supports several database engines, including MySQL, PostgreSQL, MariaDB, Oracle, and Microsoft SQL Server. It is designed to integrate well with other AWS native services. PlanetScale tends to be more cost-effective than many solutions due to its use of commodity-grade instance types optimally serving a user's unique workload. While both solutions are managed, RDS users often complain about having to manually manage database operations while PlanetScale is fully-managed.

PlanetScale and Amazon Aurora are both MySQL-compatible database platforms that aim to improve scalability, performance, and management of databases. PlanetScale is built on top of open-source Vitess technology, while Amazon Aurora is a cloud-native relational database service developed by AWS. Both support horizontal scaling, but their methods differ. PlanetScale offers connection pooling and load balancing through its edge infrastructure, while Aurora splits reads/writes and uses connection pooling as well. In terms of pricing, PlanetScale tends to be more cost-effective due to its use of commodity-grade instance types optimized for a user's workload. Both platforms automate basic database operations and provide monitoring, logging, and auditing solutions. However, PlanetScale offers built-in auditing and log retention, as well as integrations with popular third-party monitoring tools such as Datadog. For change management, PlanetScale provides a Git-like workflow for change management in combination with CI/CD tooling, while Amazon Aurora does not support online schema changes but can use Aurora Backtrack to restore the database to a point-in-time (PIT) to recover from DDL operations that introduce a breaking change. Overall, PlanetScale is considered by many as a superior platform due to its improved scale and performance, cost-effectiveness, and built-in CI/CD and database change management features.

Vector search and storage are being added to MySQL by PlanetScale, enabling users to utilize the platform for AI use cases without needing a separate tool. Vectors are one-dimensional arrays of real number values representing attributes or dimensions, useful in applications like machine learning where vectors are used to transform arbitrary data into a uniform numerical representation. The addition of vector storage and search will allow MySQL users to efficiently traverse graphs of vectors, quickly presenting users with similar results, reducing the need for separate databases or additional operational burden. PlanetScale is maintaining a fork of MySQL to add vector types and indexes, with plans to release new packages and containers for testing and development locally, and will automatically gain vector storage and retrieval capabilities for current customers upon launch.

PlanetScale Managed on AWS is now PCI compliant`, a significant achievement for the company, demonstrates its commitment to building enterprise-grade security at every step of its database development process. The certification, issued by Attestation of Compliance (AoC) and Report on Compliance (RoC), confirms compliance with the latest version 4.0 of the Payment Card Industry Data Security Standard (PCI DSS). This milestone marks a major step in strengthening trust with customers as PlanetScale continues to evolve its security policies, practices, and systems. The cross-functional collaboration between security, engineering, and operations teams resulted in significant improvements to authentication, logging, access management, and network security, further showcasing the company's commitment to customer trust and reliability.