How we built a serverless SQL database

Post by geoduck14 » Thu, Oct 28, 2021, 2:51 AM UTC

reilly3000 wrote: post #81

geoduck14 wrote: post #76

Earlier quoted context omitted.

I see. Looking at the docs, the pricing for storing data is measured in Gigs (I think $1 per gig per month) - not Tb. This makes me think it is intended for smallish data. I have a database now with 40 Tb - this would cost $40k a month just to store!

Yikes! I think this is really positioned for side projects and microservices. There is a clear path to migrating to a full instance or Postgres cluster over certain usage levels, but for many cases being able to scale to zero is still economically and operationally valuable. 40Tb is a ton-o-data! Snowflake sounds like a good fit.

Yeah, they get style points for "scaling to zero". I've seen plenty of vendors who "are scalable" - but with a floor of $70k/yr.

I like their product offering - I'd be interested in using them for hobby projects, but not for work atm.

Post by YZF » Thu, Oct 28, 2021, 6:00 AM UTC

emilsedgh wrote: post #88

YZF wrote: post #86

Earlier quoted context omitted.

This will be somebody else's problem? Ehm, no it's not. - When the bridge collapses I'll be managing someone else. - When they find out this airplane has critical design flaws I'll be managing someone else. - When this software I'm working on is hacked I'll be managing someone else.

It's not a matter of who's problem it is. It's just that a scale-able architecture in most cases is a premature optimization. When building a product, scalability is only one aspect. And in case of most startups and companies, amongst the smaller ones. I personally interview a lot of people and if they start proposing microservices or k8s or anything trendy like that (before having context), I consider it a negative…

I wasn't commenting on whether scalability is important or not. I was commenting on that mindset: "When that matters, I won't even be managing the person whose problem that is."

What you said all sounds reasonable. Sure, don't build something scalable if you've figured out you want something quick to prove your market and you're ok with tossing it all away or if you'll never need the scale. These are not the same thing. But this will be somebody else's problem? I don't want that guy on my team... Something someone told me a long time ago, write code like the guy that takes it over from you is a psychopath and has your address.

Re: How we built a serverless SQL database

Re: How we built a serverless SQL database