4 ms·
In the words of one of my former DBAs: "MySQL makes a pretty good noSQL database". That is to say you can do a quick and dirty key-value store in MySQL and it
by athenot 9y ago
In the words of one of my former DBAs: "MySQL makes a pretty good noSQL database".
That is to say you can do a quick and dirty key-value store in MySQL and it will be plenty fast. When you're ready to start normalizing things, just start pulling values out into their own columns and/or tables.
Conversely, when starting a product, don't worry about deeply normalized databases: use a relational DB as a glorified key-value store, then normalize things as you go. You'll get the best of both worlds.
- sushisource 9y agoYep. I've done the same thing by using JSONB in postgres.
- tracker1 9y agoI've done similar for most SQL databases having either an xml, or json column to store ancillary information that didn't need to be accessed or indexed in ways that aren't programmatic. For example, if you support Amazon Payments, Paypal and a payment gateway, the shape of the data for the transaction is different, and rarely looked at, why not shove it into a bigtext/blob field as xml/json.