|
|
|
|
|
|
by Incipient
47 days ago
|
|
|
The only way you can get away with creating an application without touching sql is of you offload the logic to your backend language, and then I don't think you'd be efficient enough to scale. Also can someone actually understand the logic of joins, indexes, pks, etc enough to create an efficientand scalable db, and not simply have learned sql by proximity? |
|
|
Please look at app platforms like Firebase[1]. There are absolutely complex Web applications running at scale that do not use SQL anywhere in the stack.
Aside from that, MongoDB and Redis are 17 years old; CouchDB is over 20. NoSQL is well-established at this point. All of the hyperscalers offer proprietary NoSQL databases, and have done so for years. A large number of developers uses those databases in production.
In our API-centric environment, there are a lot of apps that don't do much in the way of managing their own data directly at all, using mixtures APIs for auth and other key application functions.
> can someone actually understand the logic of joins, indexes, pks, etc enough to create an efficientand scalable db
If you are not using a relational database, these concepts do not necessarily apply.
1 - https://firebase.google.com/docs/firestore/query-data/querie...