2 ms·
The database analogy breaks down pretty quickly though. Instead of deciding what file to put something in, you have to decide which table. And you're not going
by actinium226 4y ago
The database analogy breaks down pretty quickly though. Instead of deciding what file to put something in, you have to decide which table. And you're not going to have a single database for all your code, so you'll have to decide which database to put the code in, and which table within that database.
And now we're created libraries and packages.
Not to mention that sometimes a database gets too big and performance goes down, so maybe we want to split it up or shard it or something. And I haven't even mentioned all the database types out there, relational, document, graph, time-series...