3 ms·
So what’s a good web app datastore in your opinion, if SQL is highly overrated? > Storing old data as-is What does this mean? Can you give an example?
by WA 4y ago
So what’s a good web app datastore in your opinion, if SQL is highly overrated?
> Storing old data as-is
What does this mean? Can you give an example?
- lmm 4y ago> So what’s a good web app datastore in your opinion, if SQL is highly overrated? I've used Cassandra very successfully, but there are plenty of options. > > Storing old data as-is > What does this mean? Can you give an example? I mean not migrating the stored version of old data (note I'm not suggesting "no schema" or anything like that; what I'm opposing is the idea that you have a single global mutable version of the schema and mutate historical records in place to match that). E.g. if you started by storing users with a single nationality field and then realised that actually the same user can have multiple nationalities, while you'd change the DTO representation of a user that you read into, you wouldn't rewrite the on-disk representation of previously stored users.
- dmingod666 4y agoCassandra is horribly inflexible.. you cannot use where conditions in any fields other than the PK (assuming you're not going to use ALLOW FILTERING for all your queries) and if your data isn't going to grow beyond baby size where allow filtering is okay, then you probably don't need a whole distributed java app running. Just do sqlite or newer local file storage dbs etc. SQL has earned its place due to the expressiveness and flexibility .. you may hold your opinions but you'll hardly find anyone who would take 'SQL is overrated' seriously.
- nicky0 4y agoIt means instead of migrating the database, you just leave it as it is. New code will expect to see both the old and new record formats.