> Databases are a great piece of technology! Learning how to use them properly can have huge payoff in terms of business value generation. Certainly. Is a bit

> Databases are a great piece of technology! Learning how to use them properly can have huge payoff in terms of business value generation. Certainly. Is a bit sad that the most well known are applications made for users (most RDBMS) instead of for developers, combined with a glorified DSL (SQL) that has never been made for make code at "large", not even at the scale of Lua or similar. I worked with FoxPro and do all the DB code was not only a joy, it makes too much sense! Thinking that interface with the network to store some meager byte on a disk is normal, that use terrible languages for data programming (not only SQL but JS, C# or whatever) is fine is baffling. But well. In terms of what is available: * RDBMS despite being applications (including sqlite) and not developer frameworks are plenty flexible and powerful for at least solve most data-oriented coding "DATA"-oriented is the key: Is wrong to say "this is backend, frontend, ui, etc" that is more a deployment issue and totally orthogonal. The most obvious example is the effect of N+1 queries: You are not thinking in what is data-oriented and using a incorrect programming language to solve what even an anemic DSL like SQL do much better. With the right mental model, is so easy to build a database schema with types, functions, procedures, views(that are so underused!) and such that make the clients DUMB. IS MUCH EASIER! And I work with ERPs, that are much more "complicated" than the median app. Let the DB do what it does well and the rest will be simplified by leaps and bounds. Even testing, just not commit the stupid mistake of use "mocks" that should be mocked and just spin ephemeral dbs/schemas. Is fast (even with PG) and will not create tons of churn because your regular langs is not ACID but the DB is.