3 ms·
I think the other point of contention was your term "database". There are lots and lots of systems out there that rely on data that is not stored in a database
by kasey_junk 11y ago
I think the other point of contention was your term "database". There are lots and lots of systems out there that rely on data that is not stored in a database. The data is the same kinds of things you would store in a databases but they exist as files on a filesystem instead (or in another data storage devices that is usually not referred to as a database).
That said you could easily use the same advice for that data. But in some cases the application itself needs to be on the same server as the database. Think if you were building postgres for instance...
- vinceguidry 11y ago> There are lots and lots of systems out there that rely on data that is not stored in a database. The data is the same kinds of things you would store in a databases but they exist as files on a filesystem instead (or in another data storage devices that is usually not referred to as a database). If you can't afford to lose it, then it needs to be appropriately managed so it can be recreated in the case that it's lost. If you can afford to lose it, then it's not really state and you can forget about it.
- derefr 11y ago"Files on a file system", on a server dedicated to holding files, could be termed an object store. S3 is a database.
- kasey_junk 11y agoAgreed. But that is a increasingly rarer understanding of the term database.
- derefr 11y agoI think people will understand more easily if instead of saying "database" specifically, you say "database tier." I'm pretty sure the usual understanding of the terms "business tier" and "database tier" is that the "business tier" is a bunch of ephemeral nodes, and the "database tier" is where-ever the data from the "business tier" goes to be persisted.