Suddenly, I realized: fluids are in, animals are out. The big data ecosystem has given up on its elephants, impalas and pigs in favor of aquatics. Perhaps, the shift started with “data lakes,” or, perhaps, data lakes just reflected the state of big data (pun intended). Or maybe, Cascading was the one that signified the shift: Cascading was the first to enable data application development on Apache Hadoop, leaving developers Driven, Lingual and Scalding. It is now obviously Fluid.
According to Metanautix, navigating data has never been so fluid. Did you notice not just nautix, but also meta in the name? This is for a good reason. Metadata is key to deriving value from big data. Tonight (23 October), I am moderating a panel on enabling Hadoop data, so that a data lake wouldn’t turn into a data marsh. Incidentally, one of the panelists is Waterline Data Science. If you are in the Bay Area, come see the panel in person in Sunnyvale — everyone is welcome.
Big data is flowing through all kinds of data pipelines and is streaming from all things, up to the point of becoming a DataTorrent. It can run freely in its purest state — H2O, or get sublimated into Snowflake in the cloud. If weather permits, data could even pour like FirstRain (a company that trademarked the term Personal Business Analytics!).
You might wonder whether the current big data darling Spark fits into the Age of Aquarius picture. It does — how about a killer app Sparkling Water? The new wave of big data technologies is rising!
Follow Svetlana on Twitter @Sve_Sic
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.