<?xml version="1.0"?>
<rss version="2.0">
   <channel>
      <title>Data lakes by </title>
      <link>https://padlet.com/a_copeland/data_lake</link>
      <description>TASK - You have been asked to investigate the possible benefits of creating a data lake for the organisation you work for.  What tools would you suggest using to implement this.</description>
      <language>en-us</language>
      <pubDate>2018-10-15 12:49:07 UTC</pubDate>
      <lastBuildDate>2018-10-17 15:10:36 UTC</lastBuildDate>
      <webMaster>hello@padlet.com</webMaster>
      <image>
         <url>https://padlet-assets.s3.amazonaws.com/icons/Rocket.png</url>
      </image>
      <item>
         <title></title>
         <author>johnturbefield</author>
         <link>https://padlet.com/a_copeland/data_lake/wish/292786799</link>
         <description><![CDATA[<div>Amazon cloud services (AWS).</div>]]></description>
         <enclosure url="" />
         <pubDate>2018-10-15 13:05:49 UTC</pubDate>
         <guid>https://padlet.com/a_copeland/data_lake/wish/292786799</guid>
      </item>
      <item>
         <title>Jo on Flume</title>
         <author>a_copeland</author>
         <link>https://padlet.com/a_copeland/data_lake/wish/292789685</link>
         <description><![CDATA[<div>A way of 'sucking' data out of streaming sources.&nbsp; Not sure where the data gets put. &nbsp; Maybe we use another Apache tool for storing the data</div>]]></description>
         <enclosure url="" />
         <pubDate>2018-10-15 13:10:47 UTC</pubDate>
         <guid>https://padlet.com/a_copeland/data_lake/wish/292789685</guid>
      </item>
      <item>
         <title>Jo on Impala</title>
         <author>a_copeland</author>
         <link>https://padlet.com/a_copeland/data_lake/wish/292790435</link>
         <description><![CDATA[<div>A database.&nbsp; ?? Use Flume to get the data, Impala to store and Spark to query it.&nbsp;<br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-10-15 13:12:03 UTC</pubDate>
         <guid>https://padlet.com/a_copeland/data_lake/wish/292790435</guid>
      </item>
      <item>
         <title>John T on Amazon</title>
         <author>a_copeland</author>
         <link>https://padlet.com/a_copeland/data_lake/wish/292790975</link>
         <description><![CDATA[<div>Amazon have tools to do just about everything for data science.<br><br>Amazon Web Solutions have a wide variety of tools.&nbsp; You can buy these for below cost<br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-10-15 13:12:55 UTC</pubDate>
         <guid>https://padlet.com/a_copeland/data_lake/wish/292790975</guid>
      </item>
      <item>
         <title>Tim on Data Lakes</title>
         <author>a_copeland</author>
         <link>https://padlet.com/a_copeland/data_lake/wish/292791685</link>
         <description><![CDATA[<div>Microsoft, IBM, Oracle, Amazon, Cap Gemini all have different tools for creating data lakes.&nbsp;<br><br>When configuring one of these for an organisation you need to check the architecture is in place so that it can be 'vendor' neutral.&nbsp; &nbsp; E.g. Cap Gemini are using the data warehousing solution from EMC.&nbsp; You don't want to be trapped with a particular product because the whole idea of data lake is that they are application/solution neutral/independent.&nbsp;<br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-10-15 13:14:09 UTC</pubDate>
         <guid>https://padlet.com/a_copeland/data_lake/wish/292791685</guid>
      </item>
      <item>
         <title>Jo on Data Lakes</title>
         <author>a_copeland</author>
         <link>https://padlet.com/a_copeland/data_lake/wish/292793688</link>
         <description><![CDATA[<div>AWS ship with the Apache tools</div>]]></description>
         <enclosure url="" />
         <pubDate>2018-10-15 13:17:31 UTC</pubDate>
         <guid>https://padlet.com/a_copeland/data_lake/wish/292793688</guid>
      </item>
      <item>
         <title>Tim</title>
         <author>a_copeland</author>
         <link>https://padlet.com/a_copeland/data_lake/wish/292794333</link>
         <description><![CDATA[<div>Databases should be tailored to a specific industry: analytics need are industry specific.&nbsp;<br><br>Automated Metadata management - this is important for a data lake and the requirements will be specific to the industry/application.<br><br>Need to avoid data swamp situation (add a suitable filtration system)</div>]]></description>
         <enclosure url="" />
         <pubDate>2018-10-15 13:18:29 UTC</pubDate>
         <guid>https://padlet.com/a_copeland/data_lake/wish/292794333</guid>
      </item>
      <item>
         <title>From Tim</title>
         <author>a_copeland</author>
         <link>https://padlet.com/a_copeland/data_lake/wish/292879578</link>
         <description><![CDATA[<div>Data lake</div><div>A data lake:</div><div>* a single platform combining storage, data governance, and analytics</div><div>* Designed to address these challenges.</div><div>* Centralized, secure, and durable cloud-based storage platform that allows you to ingest and store structured and unstructured data, and transform these raw data assets as needed.</div><div>* You don’t need an innovation-limiting pre-defined schema.</div><div>* You can use a complete portfolio of data exploration, reporting, analytics, machine learning, and visualization tools on the data.</div><div>* Makes data and the optimal analytics tools available to more users, across more lines of business.</div><div>* Enables users to get all of the business insights they need, whenever they need them.</div><div>With a data lake, you can do the following:</div><div>* Ingest and store data from a wide variety of sources into a centralized platform.</div><div>* Build a comprehensive data catalog to find and use data assets stored in the data lake.</div><div>* Secure, protect, and manage all of the data stored in the data lake.</div><div>* Use tools and policies to monitor, analyze, and optimize infrastructure and data.</div><div>* Transform raw data assets in place into optimized usable formats.</div><div>* Query data assets in place.</div><div>* Use a broad and deep portfolio of data analytics, data science, machine learning, and visualization tools.</div><div><br></div><div><br></div><div><br></div><div>The Data Lake can be an effective data management solution for advanced analytics experts and business users alike. A Data Lake allows users to analyze a large variety and volume when and how they want. Following a Data and Analytics as a Service (DAaaS) model provides users with on-demand, self-serve data.</div><div>However, to be successful, a Data Lake needs to leverage a multitude of products while being tailored to the industry and providing users with extensive, scalable customization.</div><div><br></div><div>Characteristics of a Successful Data Lake Implementation</div><div>A Data Lake enables users to analyze the full variety and volume of data stored in the lake. This necessitates features and functionalities to secure and curate the data, and then to run analytics, visualization, and reporting on it. The characteristics of a successful Data Lake include:</div><div>Use of multiple tools and products.</div><div>Extracting maximum value out of the Data Lake requires customized management and integration that are currently unavailable from any single open-source platform or commercial product vendor. The cross-engine integration necessary for a successful Data Lake requires multiple technology stacks that natively support structured, semi-structured, and unstructured data types.</div><div>Domain specification.</div><div>The Data Lake must be tailored to the specific industry. A Data Lake customized for biomedical research would be significantly different from one tailored to financial services. The Data Lake requires a business-aware data-locating capability that enables business users to find, explore, understand, and trust the data. This search capability needs to provide an intuitive means for navigation, including key word, faceted, and graphical search. Under the covers, such a capability requires sophisticated business ontologies, within which business terminology can be mapped to the physical data. The tools used should enable independence from IT so that business users can obtain the data they need when they need it and can analyze it as necessary, without IT intervention.</div><div>Automated metadata management.</div><div>The Data Lake concept relies on capturing a robust set of attributes for every piece of content within the lake. Attributes like data lineage, data quality, and usage history are vital to usability. Maintaining this metadata requires a highly-automated metadata extraction, capture, and tracking facility. Without a high-degree of automated and mandatory metadata management, a Data Lake will rapidly become a Data Swamp.</div><div>Configurable ingestion workflows.</div><div>In a thriving Data Lake, new sources of external information will be continually discovered by business users. These new sources need to be rapidly on-boarded to avoid frustration and to realize immediate opportunities. A configuration-driven, ingestion workflow mechanism can provide a high level of reuse, enabling easy, secure, and trackable content ingestion from new sources.</div><div>Integrate with the existing environment.</div><div>The Data Lake needs to meld into and support the existing enterprise data management paradigms, tools, and methods. It needs a supervisor that integrates and manages, when required, existing data</div><div>management tools, such as data profiling, data mastering and cleansing, and data masking technologies.</div><div>Keeping all of these elements in mind is critical for the design of a successful Data Lake.</div><div>https://knowledgent.com/whitepaper/design-successful-data-lake/ https://docs.aws.amazon.com/aws-technical-content/latest/building-data-lakes/building-data-lakes-on-aws.pdf</div>]]></description>
         <enclosure url="" />
         <pubDate>2018-10-15 15:26:26 UTC</pubDate>
         <guid>https://padlet.com/a_copeland/data_lake/wish/292879578</guid>
      </item>
   </channel>
</rss>
