News for hackers. Stuff that matters.
Re:PlanetScale for Postgres is now GA by sreekanth850 on Monday September 22, 2025 @11:21PM (#45342484)
No matter if its hosted on Azure GCP or AWS, latency is real. Cloud providers doesn't magically eliminates the Geography and phhysics. Private network don't eliminates latency magically. In general, Any small latency hike can potentially create performance bottlenecks for write operations in strong consistency DB like postgres or MySQL because each write operation go through a round trip from your server to remote planetscale server that create transaction overhead. Complex transactions with multiple statements can amplify this latency due to this round trip. But you could potentially reduce this latency by hosting your app near to where planet scale host their DB cluster though. But that is a dependency or compromise. Edit: A few writes per second? Probably fine. Hundreds of writes per second? Those extra milliseconds become a real bottleneck.
Re:PlanetScale for Postgres is now GA by mattrobenolt on Tuesday September 23, 2025 @12:13AM (#45342779)
You can simply place your database in the same AWS or GCP region and the same AZs.
Re:PlanetScale for Postgres is now GA by aiisthefiture on Tuesday September 23, 2025 @03:42AM (#45343966)
Your database will get slower before the latency is an issue.
Re:PlanetScale for Postgres is now GA by hobofan on Tuesday September 23, 2025 @04:16AM (#45344248)
> Hundreds of writes per second? Those extra milliseconds become a real bottleneck.

Of course it's nicer if the database can handle it, but if you are doing hundreds of sequential non-pipelined writes per second, there is a good chance that there is something wrong with your application logic.

Re:PlanetScale for Postgres is now GA by sreekanth850 on Tuesday September 23, 2025 @07:53AM (#45345693)
Not universal, there are systems that need high frequency, low latency, strong consistency, writes.
Re:PlanetScale for Postgres is now GA by hobofan on Tuesday September 23, 2025 @01:57PM (#45350587)
Yes, but for the majority of those, rhose would be individial transactions per e.g. request, so the impact would be a fixed latency penalty rather than a multiplicative one.