4 ms·
Adding in a service like a SQL database because "you might want that" in the future is not a good idea. Apps should do what they need to do and no more. "Future
by onion2k 6y ago
Adding in a service like a SQL database because "you might want that" in the future is not a good idea. Apps should do what they need to do and no more. "Future proofing" is almost always a waste of time - even if you definitely want the feature in the future it's usually better to add it in when it's needed than adding it early and have to support something that adds no value yet.
As for reports and transactions specifically, noSQL databases support both.
- d1sxeyes 6y agoOP isn't talking about noSQL databases, but no database at all (if I understand correctly - OP says '- No SQL database; I just keep everything in memory in native data structures'. In this case, I don't think OP is even thinking about noSQL databases.
- kouteiheika 6y agoCorrect. Sorry, I should have worded that better; unfortunately I cannot edit the post anymore.
- arkitaip 6y agoUnless, of course, switching to SQL turns out to be a major headache because it requires major rewrites, organizational changes, etc.
- zepolen 6y ago> "Future proofing" is almost always a waste of time Not really, unless you lack the experience to know what to future proof and what not to future proof. I've saved days/weeks of development by future proofing certain things, I've also saved days/weeks of development by taking pragmatic YAGNI in the right places. Obviously this will only surface on projects that last longer than a couple months ;)