Relational Databases have been around for a long time.
And Hadoop is rising in popularity.
How about this, merge the two.
Put a files system within the Relational Database.
For example, you take SQL Server, add a Microsoft Distributed File System within it, where you can add files, and then access it's data, combined.
Having a file system within the database makes sense, why keep them separate.
A single place to store data, mashing up structured and non-structured data via SQL.
And what would be the next obvious evolution, right, move it to the cloud.
Why have two separate systems, why not leverage the existing Database with all it's ETL and Business Intelligence features and combine it with Big Data. No need to let the two systems talk to each other, have just one system.
I'm not sure why Hadoop doesn't have much competition in the file system distributed architecture.
Seems like the vendors would hop on board and add their own merged Relational / File System databases.
Maybe it's just a matter of time.
I signed up for the Hortonworks Certified Associate exam last Thursday. Figured if I sign up, I'd have to take the test. And if I tak...
Saw a post today on Twitter, " Microsoft releases CNTK, its open source deep learning toolkit, on GitHub " This is big news. Be...
It seems like open source applications are the mainstream today. So many new products delivered through Aache foundation. Some do this. S...