HN Explorer

Ask HN: Is anyone use Cloud based SQL databases anymore?

5 points by RonnieOwnsLexus ↗ HN
Almost all of greenfield projects that I see in my team are using nosql. The senior developers and architects I interact with often making a case that the simplicity of no schema and the lack of complexity in designing a relation schema. Even when the tradeoff are called out (lack of complex joins and more cost).

So I am curious if that is the slowly becoming the industry norm or now?

Is anyone using nosql databases in the cloud any more ? If yes then what for what use case ?

6 comments

[ 3.1 ms ] story [ 27.2 ms ] thread
1xdevloper
After evaluating several SQL and NoSQL services I ended up using Planetscale for my chrome extension Autotype[1]. I have a single db with tables to store user accounts, rich text shortcuts, role based access controls etc. I use Cloudflare workers and Planetscale's serverless library to interact with the db. The pricing is reasonable and the developer experience is great for an indie hacker like me.

[1] https://chrome.google.com/webstore/detail/autotype-free-text...

sharemywin
does it look at credit card numbers?
1xdevloper
My extension? It doesn't do any parsing, just stores whatever content is saved securely in the db. But you shouldn't ever save any sensitive data like this though.
AYBABTME
I'm curious what your environment is like, because my experience has been the opposite. No one that I know would recommend a nosql database in the vast majority of cases. Especially since there's great offerings out there nowadays, and plenty of proven experience with stuff like MySQL (most often with Vitess) supporting super high loads such as Youtube, Shopify, GitHub, etc. MySQL scales for a lonnnnng time. And the same is true for Postgres, with multiple hosted offerings and also reimplementations that are PG compatible.

My experience is that NoSQL databases are used in last resort situations: you _need_ Cassandra, etcd, ElasticSearch for XYZ reason, as a dependency to another distributed system. But I haven't seen anyone suggest actually using stuff like MongoDB and the likes.

audioheavy
There's definitely interest in both, but oftentimes for what I would argue are the wrong reasons. MySQL and PostgreSQL scale to a point but with complexity and data isolation limitations, but they will be always popular because of their longevity. Some NoSQL options scale better horizontally but the limitations of isolation levels are even more significant. Just because most of them now can handle ACID transactions and some form of joins does not mean they can handle strict serialization at scale. There are some, like Fauna, that do, however.
AYBABTME
My experience is that MySQL scales as high as you need it when coupled with Vitess, because most data schemas can be sharded, and you can scale each shard vertically enough for all the workloads I've seen.