samlambert

6 ms·

61.
by samlambert 11mo ago
This is not true. All of our Vitess operations assume 3 node clusters. It's a lot of work to change (we have hundreds of thousands of nodes). For Postgres it was a lot simpler to do based on the architecture. There are equally good thi
62.
by samlambert 11mo ago
we are working on the open source licensed version.
63.
by samlambert 11mo ago
but its entry level pricing for customers that grow. it will be great for us. there is no point hurting our reputation and slowing growth.
64.
by samlambert 11mo ago
this makes no sense to me
65.
by samlambert 11mo ago
pull the rug on what? a profitable product?
66.
by samlambert 11mo ago
data is still replicated safely from the single node which is also backed by EBS.
67.
by samlambert 11mo ago
thank you
68.
by samlambert 11mo ago
you have to make sure you will never terminate these nodes, that you have all the operations maturity to cycle them responsibly, and resize them. I am sure they will get there one day but most people are still figuring out how to run databa
69.
by samlambert 11mo ago
the reason we make sure all our products are gross margin positive is so this doesn't have to happen.
70.
by samlambert 11mo ago
why is it going to the mat? i had to correct something that was untrue. 1.5 years is not very recently.
71.
by samlambert 11mo ago
It's very hard to do. They all want to do it but can't so now it's their marketing team's jobs to lie to people about why they shouldn't want it.
72.
by samlambert 11mo ago
Why would we? we make a (small) profit on these cheaper tiers. We are a sustainable and profitable company. Also the free tier wasnt cancelled very recently it was 1.5 years ago so you are reaching a bit here.
73.
by samlambert 11mo ago
it's a 70% difference at lower cost. i know math is hard but c'mon try and be serious.
74.
Migrating Supernova to PlanetScale: Faster APIs, Better Insights(getsupernova.ai)
4 points by samlambert 11mo ago|0 comments
75.
by samlambert 1y ago
We run 3 nodes not 1. Your comment is not in isolation we get constant shade from Timescale people when we don't even think about you.
76.
by samlambert 1y ago
Agreed on these trade offs. We do both synchronous and semi-synchronous depending on Postgres or MySQL.
77.
by samlambert 1y ago
While this post is here I'd like to call out that Vitess for Postgres is coming https://www.neki.dev/
78.
by samlambert 1y ago
Correct. Network storage is flexible for a variety of use cases that's why PlanetScale supports both.
79.
by samlambert 1y ago
We are working on it.
80.
by samlambert 1y ago
we have mitigated the durability concerns in multiple ways.
81.
by samlambert 1y ago
What is wrong with running without lots of abstractions? We are clear about the downsides. The results are clear, you can see the customers love it. We run insane amounts of state safely on ephemeral compute. It's a flex. All I've
82.
by samlambert 1y ago
Congrats on the launch and thank you for being a customer!
83.
by samlambert 1y ago
If anyone has questions about these principles or how we practically apply them please feel free to ask.
84.
by samlambert 1y ago
Thank you Gavin! I hope you are well.
85.
by samlambert 1y ago
if your sharding schema is designed properly you will avoid cross shard transactions.
86.
by samlambert 1y ago
Another Ben Dicken classic
87.
by samlambert 1y ago
we've seen a number of Supabase -> PlanetScale migrations and it's been pretty simple with significant cost savings for the customer. The scale part of this is hard to answer because it really depends on the workload.
88.
by samlambert 1y ago
Inspired by Vitess seeing as we are the company behind Vitess but it's a new codebase.
89.
by samlambert 1y ago
you made a dumb comment and got heat for it. i don't think that represents a narcissistic personality. regardless of what you think of us i wish you all the best.
90.
by samlambert 1y ago
happy to answer this with direct customer quotes from the companies you mentioned. all of these quotes are public: "We chose PlanetScale to host our most demanding Vitess and Postgres workloads, doing millions of queries per second on

More ›