Wondering will we see something like this for Postgres?
I like the cool things but I can’t migrate to MySQL just because of this.
back
4 comments
I've been following Citus Data, it might be interesting for you.
https://www.citusdata.com/
Ed: obviously this does not solve the bigger service of providing "magic" scale up/down, though.
It looks like the "branching schema" is essentially:
CREATE DATABASE branch_name WITH TEMPLATE main;
I might actually have to try this - I hadn't really thought template dbs would be all that useful in pg - but this branch and test för dev use-case is interesting.
Then there's COPY (for data) and rename to "promote" a branch with data (one would probably want to run DDL on main db though:
ALTER DATABASE branch_name RENAME TO main; -- would have to move old main out of the way first - but might be possible in same transaction?
Sure you can! and we will make it worth it.
I can't decide whether this joke is marketing folly or strategic genius.
On the one hand, making light of how big an undertaking a _database engine migration_ would be makes you come off sounding like the "mongodb is web scale" guy. That's a pretty terrible look for a company proposing to take on critical production infrastructure.
On the other hand, adding postgresql support to vitess is probably a _massive_ undertaking. Sure, it might make sense for you to contribute to in the long run to open up that customer segment, but at your current stage postgresql customers are probably more of a product-distraction than anything. In that light, driving us away for now is probably the best policy.
I'm gonna give you the benefit of the doubt. Well played, sir. Well played.
EDIT: nevermind, all your other comments so far in this thread are variations on "Yes, we can do that!". You're promising the moon, and that's fishy.
Bit of unsolicited advice (you know what they say about unsolicited advice, but here goes...): You'd be better off admitting some weaknesses and discussing tradeoffs. For examples, take a look at other HN threads where execs have hopped on. What qualities do you seen in posts that get the most positive responses? Now compare that to the confusion and skepticism in this thread. Your messaging has landed off-target.
You're proposing to take over a piece of people's critical production infrastructure. As a potential buyer considering an infrastructure provider, seeing "buy our product and we'll solve all your problems" just makes me skeptical. It makes you sound like a used car salesman. Your landing page delivers that basic message, and your comments in this thread reinforce the resulting impression.
Conversely, if in these comments you soberly acknowledged your limitations, transitioned to a detailed treatment about tradeoffs, and _then_ used that save to toot your horn some more, that would give the impression you've considered this problem deeply, help me figure out how closely your value prop is aligned to my goals, and make me more inclined to trust you, your company, and your product.
As it is...
I see your comment and it makes me think your company isn't ready to take on my infrastructure (this is my database we're talking about here... if you're not taking something as basic as migration costs seriously, what other nasty surprises are waiting for me down the line?).
Then, I take a look at your about page (maybe this guy's just an entry-level marketer in the people-pleaser phase), and I see that you, Sam Lambert, are the Chief Product Officer. That gives me some serious doubts about the future viability of your company, because now I'm worried the CPO is fundamentally out of touch with the userbase and can't grapple with difficult details.
You will not be touching my data any time soon, but I'll be watching for changes, and I honestly wish you luck. I like your vision, but your messaging execution needs work and your product execution is yet-unproven.
EDIT: kudos to lizztheblizz for giving more detailed answers that inspire confidence. You've significantly repaired my impressions of your company.
We are definitely not out of touch with our user base. The reason I feel a high degree of confidence is that we currently have a major Postgres user moving to PlanetScale at the moment and they are loving the experience. This is v1 of our product. I have not seen a database product like this, that cares about the daily lives of the users that use it. I believe we can create a fundamental shift in how databases think about their users.
We concern ourselves with the productivity of our users. We also solve hard problems at scale, for many large companies. We have so many exciting developer focussed features that I think people will love, all the while being on a viable database. Vitess is by far the highest scale open source database solution out there.
Migration cost is a serious thing. We believe the immense leap in productivity you will gain over time from our product makes it more than worth it.
Despite the partial retraction this is great advice, hope I’ll get that level of quality feedback on a projects.
looks like it's a ways off... planetscale says they're built on vitess, and vitess has postgres compatibility at the bottom of their "Medium Term" roadmap: https://vitess.io/docs/resources/roadmap/
It has been there for two plus years with very little news and development. I wouldn't expect it to be done in another 3-4 years.