September 2025 Summaries
4 posts from PlanetScale
Filter
Month:
Year:
Post Summaries
Back to Blog
PlanetScale has announced a partnership with Cloudflare to streamline the deployment of full-stack applications supported by Postgres or MySQL databases. This collaboration enables seamless integration between Cloudflare Workers and PlanetScale databases, aiming to enhance application performance and reliability. Through this partnership, users benefit from faster setup with Hyperdrive, which offers connection pooling and query caching, reduced latency due to edge caching, and improved reliability from the combined infrastructure of PlanetScale and Cloudflare. This integration supports both Postgres and Vitess databases and is particularly advantageous for users facing connection limits or latency issues in serverless applications. To utilize this service, users need accounts with both Cloudflare and PlanetScale and can initiate the connection from either platform's dashboard.
Sep 24, 2025
427 words in the original blog post.
Processes and threads are essential abstractions provided by modern operating systems, enabling multitasking and resource sharing on computers. A process is an instance of a program being executed, allowing the CPU to switch between multiple tasks, thereby giving the illusion of simultaneous execution. Threads, on the other hand, allow multitasking within a single process, sharing the same memory space, and are more efficient than process context switches. The article illustrates the differences and functionalities of processes and threads through examples, such as the connection-per-process model used by Postgres and the thread-per-connection model by MySQL, highlighting how these systems manage multitasking and performance. Additionally, it touches upon the role of CPU and RAM in executing instructions, the concept of context switching, and the use of connection pooling to manage high connection demands in databases. Understanding these concepts helps in designing software that efficiently balances performance and resource management.
Sep 24, 2025
2,674 words in the original blog post.
PlanetScale has announced the general availability of PlanetScale for Postgres, a service designed to provide fast and reliable databases with an enhanced developer experience. Building on five years of success with their managed Vitess product, PlanetScale aims to offer similar scalability and performance benefits to Postgres users. The service promises an effective migration process for those transitioning from other Postgres providers and highlights customer success stories to demonstrate its capabilities. Additionally, PlanetScale is developing Neki, a Postgres sharding solution that combines elements of Vitess and Postgres, which will eventually be released as an open-source project to handle demanding workloads.
Sep 22, 2025
347 words in the original blog post.
PostgreSQL's replication design for high availability (HA) with Change Data Capture (CDC) imposes constraints that can complicate operational coupling and flexibility, primarily due to its reliance on logical replication slots. In a typical HA setup, a primary PostgreSQL server is paired with semi-synchronous standbys, and a CDC client reads from a logical replication slot. This setup can lead to issues during failover, as logical slots must be synchronized across nodes, and a standby only becomes eligible to carry a slot after the CDC client has advanced the slot while the standby is receiving metadata. This results in potential delays or breakage of the CDC stream if the client is offline or lags, as new or restarted standbys remain ineligible for slot promotion. In contrast, MySQL's approach using GTIDs and binlogs provides more flexibility, as it allows for seamless failover without the tight coupling of logical slots. MySQL enables replicas to re-emit transactions into their own binlogs, maintaining GTID continuity, and allowing CDC connectors to resume from the last committed GTID, regardless of polling frequency. This fundamental difference highlights the brittleness of PostgreSQL's HA with logical consumers, where slot progress coordination across the cluster is crucial and dependent on subscriber behavior, potentially leading to switchover delays or CDC disruptions.
Sep 12, 2025
1,174 words in the original blog post.