Are you ever, like me, shocked at the smorgasbord of RDBMSes that some projects seem to want to use these days? Sometimes it seems like database management systems that someone on the project’s sister’s cousin’s aunt heard of are used. A colleague of mine shared with me that a project he’s working on is using MongoDB, S3, DynamoDB, and MySQL. I suspect that if I actually researched some of those, I might argue with whether they’re fully featured DBMSes or not, and at least one of them is not necessarily Relational. I do tend to have a bias against the small guys. But still, that’s 4 different pieces of database software, where I’m guessing they don’t have experts in each to implement and provide expert ongoing support. It sure seems to me that it’s likely that one relational database management system would be simpler to support.
Yesterday, I ran into this great diagram: https://hpi.de/fileadmin/user_upload/fachgebiete/naumann/projekte/RDBMSGenealogy/RDBMS_Genealogy_V6.pdf
I nodded my head a little and laughed a little. Go check it out and see what you think. Now I just have to figure out how to get a poster of it.
It was reading Henrik Loeser’s blog that I learned about it – a blog that sometimes covers interesting topics.
I am ALWAYS covering interesting topics. Only the target audience changes for the posts… 😉
Well, yes, I can see that. Much as I love the beautiful lakes in your part of the world, I can’t exactly recommend them as compelling DB2-related content. Your Technical content is spot-on, you just tend to cover a wider range of interests than I do, let’s say. =)