Let's be honest, the 'Data Lake' is one of the latest buzz-words everyone is talking about. Like many buzzwords, few really know how to explain what it is, what it is supposed to do, and/or how to design and build one. As pervasive as they appear to be, you may be surprised to learn that Gartner predicts that only 15% of data lake projects make it into production. Forrester predicts that 33% of enterprises will take their attempted data lake projects off life-support. That's scary! Data lakes are about getting value from enterprise data, and, given these statistics, its nirvana appears to be quite elusive. I'd like to change that and share my thoughts and hopefully providing some guidance for your consideration on how to design, build, and use a successful data lake: An agile data lake. Why agile? Because to be successful, it needs to be. Ok, to start, let's look at the Wikipedia definition for what a data lake is:
I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too.
Stay tuned to my blog, twitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.
big data,data lakes,big data adoption,agile data
Stay tuned to my blog, twitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.
This article is related to
big data,data lakes,big data adoption,agile data
No comments:
Post a Comment