It’s not your father’s database
2 November 2012
I liked this short article below on not using SQL databases for large datasets. One of my long-time pet peeves has been designs that use SQL for configuration and extremely small data, especially < 10s of records. Oh we need to store something, lets put it in the database since we have one!
Twisting and turning data into code has been a has always been a troublesome area for software and databases add layers, which are not always good ignoring encapsulation. My mantra about this has always been don’t think SQL databases unless your problem is a *many* problem. Now I have to modify my mantra somehow that to consider the too many problem as well. Perhaps, SQL is a only an enough, but not too many solution. Help! 😉 Kenny