One "logical" Database: It's more than meets the eye
Posted by Keegan Skidmore on Tue, Feb 09, 2010
So the other day, while I was on my flight to San Diego, I found myself watching the movie Transformers over the shoulder of the person in front of me. And while I was watching Transformers over this man’s shoulder, without any sound to speak of, I found myself daydreaming about something quite interesting—databases. Databases? That’s right databases (not Megan Fox?). Not that I particularly like databases. They’re okay I guess—as databases go. But databases just seemed to be something I’ve been hearing about a lot recently. As media companies diversify their product offering with websites, microsites and e-editions. And look to extend that further into the e-readers and iPads of the world; content is becoming complicated. And media companies are finding there’s no simple solution to storing it.
Though the question is important, as of yet, there doesn’t seem to be a clear cut consensus on the best answer out there. For the most part the debate ranges between two modes of thought. One that touts the benefits of a single database and another that preaches multiple databases are the only way to go. Now, there’s nothing the hidden database techno-geek inside me would like to do more than really hack into the center of this debate—draw up diagrams, throw together some flow charts and diagnose the facts. But I can’t help thinking that’s a complete waste of time, especially when I have a movie to finish, and when there is a perfectly suitable third solution out there.
This third solution ties together the best attributes of both sides of the one vs. multiple database argument, essentially giving you the benefits of both systems without the problems of either (No way… Way). The architecture is fairly straight-forward. What people like about the one database solution is that it allows you to easily manage all of your content from the same system. There’s no going back and forth between the editorial system, the Web system, what’s being archived, etc. It’s all right there in front of you. That’s great, but can all of that content really be managed properly in a single database? I mean, it’s all so different. That’s right it is, and so no really it can’t. Ergo, the multiple database strategy. Having multiple databases is great organizationally, and solves all the problems regarding how or where to store content. But in the downside column, it can be a bit clunky to use.
Enter the one ‘logical’ database. Like Optimus Prime emerging from the blue and white Mac truck, these two options can be transformed into a solution that gives media companies the best of both solutions. With one ‘logical’ database media companies receive a single user environment to manage all of their content, while it’s being stored in multiple databases underneath. Fantastic, let’s get to the benefits.
What can media companies expect with the one ‘logical’ database solution?
First: One ‘logical’ database is going to give them a single environment to manage their content. Quick, efficient; users won’t have to be switching between disparate systems to find what they want. It will all be there and available.
Second: They’ll be able to store any type of content. Whether its user generated content, in-house created content, PDF’s, text, images, content from wire feeds or anywhere else, it won’t matter. Having multiple databases will guarantee the content is stored in the most practical location based on if it’s used for the Web, in print or needs to be archived.
Third: Prepare to integrate. With multiple databases media companies will be able to seamlessly blend third-party components into their user experience without disrupting the underlying architecture. This helps preserve the systems they have already invested in.
Fourth: Security. Believe me, if media companies were Autobots and content was their All Spark, they would love to have a one ‘logical’ database system. It would let them keep it safe and sound with the rest of their private content, while they publish everything else meant for public use. In a one database system, all content is lumped together, whether it’s public or private, meaning if the Decepticons break in, they have access to everything.
These are just a few of the benefits and media companies can expect positive results in other areas as well. But at the time, that’s all I could come up with. Blame it on the movie.