There’s been a lot of chatter recently in the blogosphere about the technical direction of the database. This discussion has been ongoing for some time and dates back to at least Bosworth’s utterings.
It kind of reminds me of the old “we’ll never use that much memory” argument, “you’ll never need more than one database”. I wonder, have we got to the point where most decent size systems be they web or enterprise will need to store more data than can be held in a single database?
Perhaps partitioning and use of dumber storage mechanisms1 will become the norm? It strikes me that this might be a more promising approach2 than attempting to build clusters when working with utility compute platforms like EC2/S3. Seems like we have some design patterns appearing, just need the frameworks to catch up?
[1] Might include RDBMS used purely for storage, containing no business logic.
[2] Partitioning might provide simpler and cheaper growth strategies than the aggravation of upgrading the server hardware for the database
Technorati Tags: architecture, storage
Entries (RSS)