Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

PlanetScale Scaler Pro

planetscale.com

Post reply on HN
Print view View original

31–40 of 44 posts

Re: PlanetScale Scaler Pro

#31

Post by Illniyar »

Am I missing something in the pricing or is the Storage costs very unappealing. For anything with a usage skewed towards high ratio of storage to usage, the costs aren't competitive.

2.5$ per GB in "Scalar" and 1.5$ per GB in "Scalar PRO" compared to 0.11$ RDS for General purpose (or 0.125$ for provisioned + the IOPS you use, double that for multi-az), Supabase at 0.125$, Firebase at 0.1725$,DynamoDB at 0.25$, MongoDB Atlas serverless at 0.25$, cockroachDB serverless at 0.5$ per GB, FaunaDB at 1$ per GB. (Neon says it's 0.000164 per GiB, but somethings seems off, it's not at the same scale, so I'm guessing there's a catch here)

Re: PlanetScale Scaler Pro

#32

Post by hu3 »

joshstrange wrote: post #16

I love PlanetScale and if I had one request it would be a plan between Hobby and Scalar (or even a way to combine multiple DBs in 1 plan, and no 2 prod branches won't cut it). I have 2 paid Scalar DBs on PlanetScale and I have no intention of moving elsewhere but it does kill me that they both sit almost unused ~10 months out of the year (I have bursty traffic and only during the events, in-person events, that the so…

I'm interested in using PlanetScale.

Would you happen to know the magnitude of how many simultaneous connections could $348/yr buy me in PlanetScale?

One of my clients hovers around 50 simultaneous connections to their main MySQL server on a normal day, but they have bursts of 3k simultaneous connections for an entire day, twice per year.

Their workload is about 5% writting (INSERTs, UPDATEs), 95% reading (SELECTS).

Re: PlanetScale Scaler Pro

#33

Post by mdasen »

slig wrote: post #30
taw1516 wrote: post #25

love PlanetScale product. Do you recommend any similar offering for PostgresSQL?

https://neon.tech/

Neon is a great suggestion. I'm just writing to add a bit more color.

Neon is a bit different from PlanetScale. With PlanetScale, they're running Vitess under the covers. Vitess is a proxy that sits between you and the MySQL database. It means they can do fancy things like rewrite the queries on the way to the database or route them differently. For example, a "SELECT" query could be sent to a replica instate of the primary. Likewise, if you've sharded/partitioned your data by customer_id, Vitess could see the query says "WHERE customer_id = 5" and send it to the correct server. This proxy also means that Vitess can seamlessly manage some things for you like failing over to a new database or bringing online a new replica.

Neon is a decoupling of storage from the database processing. While Vitess still has MySQL storing the data, Neon changes the storage so that it can separate data processing and data storage. This is somewhat like Amazon's Aurora.

If you're interested in other PostgreSQL compatible options, CockroachDB is PostgreSQL compatible, but is more of a fully distributed database from the ground up rather than new layers like Neon or PlanetScale.

Re: PlanetScale Scaler Pro

#34

Post by semiquaver »

rrdharan wrote: post #27
CtrlAltDelete51 wrote: post #18

Earlier quoted context omitted.

If they are running on AWS (which it looks like they are), they aren’t going to be able to undercut AWS. For a retail user who doesn’t want to commit to RIs or have enough volume for an EDP, sure PS can be cheaper. The value I found is being able to do multi-region read replicas with no compute overhead for lower traffic geos. I like the idea of PS and have toyed around with the idea of migrating to it but there are…

That’s not contradictory? It’s very common for scale-out architectures to read more data than is ultimately returned, because the former is pulled from individual shards and then some centralized filtering / post processing is applied in some API middleware layer. Trying to fix that by pushing down more of the query/execution is sometimes but not always feasible or practical.

(responding to GP) “Full table scans are expensive” is a better way to reframe the pricing model (at least before this pricing change). The distinction is between rows _examined_ vs rows _returned to a db client_. Even the latter is a tricky concept with vitess since it’s a routing/sharding system that sits on top of vanilla MySQL instances.

Re: PlanetScale Scaler Pro

#35

Post by purelogiq »

hu3 wrote: post #32
joshstrange wrote: post #16

I love PlanetScale and if I had one request it would be a plan between Hobby and Scalar (or even a way to combine multiple DBs in 1 plan, and no 2 prod branches won't cut it). I have 2 paid Scalar DBs on PlanetScale and I have no intention of moving elsewhere but it does kill me that they both sit almost unused ~10 months out of the year (I have bursty traffic and only during the events, in-person events, that the so…

I'm interested in using PlanetScale. Would you happen to know the magnitude of how many simultaneous connections could $348/yr buy me in PlanetScale? One of my clients hovers around 50 simultaneous connections to their main MySQL server on a normal day, but they have bursts of 3k simultaneous connections for an entire day, twice per year. Their workload is about 5% writting (INSERTs, UPDATEs), 95% reading (SELECTS).

Planetscale advertises up to 10,000 concurrent connections on their $29/mo Scalar plan (https://planetscale.com/pricing - click on "Compare all plan options and benefits"). Being based on Vitess as well, I believe that number.

Re: PlanetScale Scaler Pro

#36

Post by gsanderson »

hu3 wrote: post #32
joshstrange wrote: post #16

I love PlanetScale and if I had one request it would be a plan between Hobby and Scalar (or even a way to combine multiple DBs in 1 plan, and no 2 prod branches won't cut it). I have 2 paid Scalar DBs on PlanetScale and I have no intention of moving elsewhere but it does kill me that they both sit almost unused ~10 months out of the year (I have bursty traffic and only during the events, in-person events, that the so…

I'm interested in using PlanetScale. Would you happen to know the magnitude of how many simultaneous connections could $348/yr buy me in PlanetScale? One of my clients hovers around 50 simultaneous connections to their main MySQL server on a normal day, but they have bursts of 3k simultaneous connections for an entire day, twice per year. Their workload is about 5% writting (INSERTs, UPDATEs), 95% reading (SELECTS).

The blog post shows both the Scaler and Scaler Pro plan supporting up to 10,000 concurrent connections: https://planetscale.com/blog/announcing-scaler-pro#scaler-pr...

Re: PlanetScale Scaler Pro

#37

Post by no_wizard »

joshstrange wrote: post #16

I love PlanetScale and if I had one request it would be a plan between Hobby and Scalar (or even a way to combine multiple DBs in 1 plan, and no 2 prod branches won't cut it). I have 2 paid Scalar DBs on PlanetScale and I have no intention of moving elsewhere but it does kill me that they both sit almost unused ~10 months out of the year (I have bursty traffic and only during the events, in-person events, that the so…

you might find Supabase[0] is closer to what you need. I'd recommend giving them a look, that is, if MySQL compat isn't a requirement of course, since Supabase is all PostgresSQL.

disclosure: not a employee or investor in Supabase, but I sure am a fan.

[0]: https://supabase.com/

Re: PlanetScale Scaler Pro

#38

Post by tbarn »

hu3 wrote: post #32
joshstrange wrote: post #16

I love PlanetScale and if I had one request it would be a plan between Hobby and Scalar (or even a way to combine multiple DBs in 1 plan, and no 2 prod branches won't cut it). I have 2 paid Scalar DBs on PlanetScale and I have no intention of moving elsewhere but it does kill me that they both sit almost unused ~10 months out of the year (I have bursty traffic and only during the events, in-person events, that the so…

I'm interested in using PlanetScale. Would you happen to know the magnitude of how many simultaneous connections could $348/yr buy me in PlanetScale? One of my clients hovers around 50 simultaneous connections to their main MySQL server on a normal day, but they have bursts of 3k simultaneous connections for an entire day, twice per year. Their workload is about 5% writting (INSERTs, UPDATEs), 95% reading (SELECTS).

This number of connections on any of the paid plans should be no issue.

Re: PlanetScale Scaler Pro

#39

Post by mebcitto »

Illniyar wrote: post #31

Am I missing something in the pricing or is the Storage costs very unappealing. For anything with a usage skewed towards high ratio of storage to usage, the costs aren't competitive. 2.5$ per GB in "Scalar" and 1.5$ per GB in "Scalar PRO" compared to 0.11$ RDS for General purpose (or 0.125$ for provisioned + the IOPS you use, double that for multi-az), Supabase at 0.125$, Firebase at 0.1725$,DynamoDB at 0.25$, MongoD…

Neon price is listed as per hour, instead of per month like the others :)

While you're not necessarily missing something, it's worth pointing out that usually storage costs don't dominate the bill, the compute costs are usually higher. But with the PlanetScale storage price being more then 10x the price of the other, it's definitely something to keep in mind, and it can dominate the bill.

Post reply on HN