Databases are for storing global variables. We usually call them “rows” or “records” instead, but they’re definitionally global variables: any part of your…
The article makes a good point, but I would argue its not the whole truth.
A proper (relational) database does more than just storing values. It also stores relations between different values. And SQL is an extremely powerful way of working with those relations. I see the point that the author makes about projects with a database/state being worse, but in some projects I’ve worked on, I’ve been able to offload a great deal of work into the database schema.
And also, a database doesn’t just store a few measly little variables. Often, you’ll be storing gigabytes or more in there. That’s completely infeasible to pass from function to function, or sometimes even hold in RAM at once. The point of a database is to store and manage data, in amounts that you don’t want to have to deal with yourself.
The article makes a good point, but I would argue its not the whole truth.
A proper (relational) database does more than just storing values. It also stores relations between different values. And SQL is an extremely powerful way of working with those relations. I see the point that the author makes about projects with a database/state being worse, but in some projects I’ve worked on, I’ve been able to offload a great deal of work into the database schema.
And also, a database doesn’t just store a few measly little variables. Often, you’ll be storing gigabytes or more in there. That’s completely infeasible to pass from function to function, or sometimes even hold in RAM at once. The point of a database is to store and manage data, in amounts that you don’t want to have to deal with yourself.