I recently assisted a team implement a distributed MapReduce system for a very large dataset. The team had previously attempted to use a database to solve their business problem, but found performance to be unacceptable
The MapReduce implementation was simple and exceeded all performance requirements. However, their DBA threw fits every step of the way. To him, everything involving data could and should be solved with a SQL statement.
More and more systems use databases simply as a data archive, not for primary work. I think the DBA's are starting to be concerned that they will no longer be necessary. Obviously that isn't true, there will always be bigger and tougher problems to solve.
Slashdot Mirror
I recently assisted a team implement a distributed MapReduce system for a very large dataset. The team had previously attempted to use a database to solve their business problem, but found performance to be unacceptable
The MapReduce implementation was simple and exceeded all performance requirements. However, their DBA threw fits every step of the way. To him, everything involving data could and should be solved with a SQL statement.
More and more systems use databases simply as a data archive, not for primary work. I think the DBA's are starting to be concerned that they will no longer be necessary. Obviously that isn't true, there will always be bigger and tougher problems to solve.