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).<p>So I am curious if that is the slowly becoming the industry norm or now?<p>Is anyone using nosql databases in the cloud any more ? If yes then what for what use case ?
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.<p>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.
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.<p>[1] <a href="https://chrome.google.com/webstore/detail/autotype-free-text-expand/mgcgenippnenmppgfkbhcenpamhbbcna" rel="nofollow">https://chrome.google.com/webstore/detail/autotype-free-text...</a>