5 ms·
Yeah, I can see this argument going either way. If you're avoiding SQL for NoSQL for scalability reasons, that might be premature optimization, especially if yo
by _delirium 15y ago
Yeah, I can see this argument going either way. If you're avoiding SQL for NoSQL for scalability reasons, that might be premature optimization, especially if your data is pretty easily relational (and e.g. you have something approximating a schema).
But if you just need to persist a data model, don't care too much about the schema, and come up with the solution of, "I'll just serialize my hash table to a CSV flat file", that's just taking the ultra-simple solution, not really an optimization. If anything, pulling out the big iron of SQL when all you need to do is serialize a hashtable would be the premature optimization (or at least, premature architecting).