Selecting a Data Lake ETL Platform? Here Are 6 Questions to Ask
Not all data lakes are created equal. If your organization wants to adopt a data lake solution to simplify and more easily operate your IT infrastructure and store enormous quantities of data without requiring extended data transformation, then go for it.
But before you do, understand that simply dumping all your data into object storage such as AWS S3 doesn’t exactly mean you will have a working data lake.
The ability to use that data in analytics or machine learning requires converting that raw information into organized datasets you can use for SQL queries, and this can only be done via extract-transform-load (ETL) flows.
Data lake ETL platforms are available in a full range of options – from open-source to managed solutions to custom-built. Whichever tool you select, it’s important to differentiate data lake ETL challenges from traditional database ELT demands – and seek the platform that overcomes these obstacles.
Ask yourself which ETL solution:
1. Effectively Conducts Stateful Transformations
Traditional ETL frameworks allow for stateful operations like joins and aggregations to enable analysts to work with data from multiple sources; this is difficult to implement with a decoupled architecture.
Stateful transformations can occur by relying on extract-load-transform (ELT) – i.e., sending data to an “intermediary” database and using the database’s SQL, processing power and already amassed historical data. After transformation, the information is loaded into the data warehouse tables.
Data lakes, aiming to reduce cost and complexity by avoiding decoupled architecture, cannot depend on databases for every activity. You’ll need to look for an ETL tool that can conduct stateful transformations in-memory and needs no additional database to sustain joins and aggregations.
2 Extracts Schema from Raw Data
Organizations customarily use data lakes as a storehouse for raw data in a structured or semi-structured arrangement vs databases, which are predicated on structured tables. This poses numerous challenges.
One, in order to query data, can the data lake ETL tool draw out a schema (without which querying is not possible) from the raw data – and bring it up to date as changes in data and data structure come about? And two — this is an ongoing struggle — can the ETL tool effectively make queries with nested data?
3 Improves Query Performance Via Optimized Object Storage
Have you tried to read raw data straight from a data lake? Unlike using a database’s optimized file system that quickly sends back query results, doing the same operation with a data lake can be quite frustrating performance-wise.
To get optimal results, your ETL framework should continually store data in columnar formats and merge small files to the 200mb-1gb range. Unlike traditional ELT tools that only need to write the data once to its target database, data lake ETL should support the ability to write multiple copies of the same data based on the queries you will want to run and the various optimizations required for your query engines to be performant.
4 Easily Integrates with the Metadata Catalog
You’ve chosen the data lake approach for its flexibility — store large quantities if data now but analyze it later — and the ability to handle a wide range of analytics use cases. Such an open architecture should keep metadata separate from the engine that queries it, so you can easily change these query engines or use several simultaneously for the same data.
This means the data lake tool you select should reinforce this open architecture, i.e., be seamlessly merged with the metadata catalog. This allows the metadata to be easily “queryable” by various services because it is both stored in the catalog and still dovetails with every adjustment in schema, partition, and location of objects.
5 Replays Historical Data
Say you wanted to test a hypothesis by looking at stored data on a historical basis. This is difficult to accomplish with the traditional database option, where data is stored in a mutable condition, and in which running such a query could be prohibitive in terms of cost, stress, and tension between operations and analysis.
It’s easy to do with a data lake. In data lakes, stored raw data remains continuously available – it only transformed after extraction. Therefore, having a data lake allows you got “travel back in time,” seeing the exact state of the data as it was collected.
“Traditional” databases don’t allow for that, as the data is only stored in its transformed state.
6 Updates Tables Periodically
Data lakes, unlike databases that allow you to update and make deletions to tables, contain partitioned files that enable an append or add-only feature. If you want to store transactional data, implement change data capture in the data lake, or delete particular data for GDPR compliance, you’ll have difficulty doing so.
Make sure that the data lake ETL tools you choose have the ability to sidestep this obstacle. Your solution should be able to allow upserts, a system that lets you insert new records or update existing ones, in the storage layer and in the output tables.
About the author: Ori Rafael is the CEO and co-founder of Upsolver, a provider of a self-service data lake ETL platform that bridges the gap between data lakes and data consumers. Ori has worked in IT for nearly two decades and has an MBA from Tel Aviv University.
December 9, 2019
- TIBCO’s Connected Intelligence Platform Supports FIA Formula One World Drivers’ Championship
- Three Providers of Open Source Object Storage for High Performance Workloads Named IDC Innovators
- Diamanti Introduces GPU Platform to Support Containerized Workloads on Kubernetes
December 6, 2019
- Scalyr Named as a Representative Vendor in AIOps Platforms by Gartner
- Sapience Analytics 6.5 Draws More Faceted Picture with Workforce Data
- Study: Businesses Recognize Importance of Digital Transformation but Struggle with Limited Resources
- NFL and AWS Partner to Transform Player Health and Safety via Predictive Analytics
- Denodo Platform Now Available on Google Cloud Platform Marketplace
- Pitney Bowes Data Now Available in AWS Data Exchange
December 5, 2019
- MemSQL Announces the General Availability of MemSQL 7.0
- DDN Recognized by IDC as Fastest Growing Supplier of All-Flash Arrays
- Alibaba Cloud Releases Machine Learning Algorithm Platform on Github
- Looker Achieves AWS Retail Competency Status and Amazon Redshift Ready Designation
- Qumulo and iTernity Announce New Partnership at HPE Discover More Munich
- Spectra Logic Announces General Availability of StorCycle
- BigID Announces AWS Security Hub Integration, AWS Marketplace Availability
- Talend Achieves AWS Retail Competency Status
- Snowflake Expands AWS Partnership, Achieves AWS ML, AI Competency Status
- Data Engineering, Data Lake, and Enterprise Data Warehouse Solutions from Informatica Now Available on AWS
- Purdue Announces Plans to Build New Data Science Building
Most Read Features
- Deep Learning Has Hit a Wall, Intel’s Rao Says
- Big Data File Formats Demystified
- Will Databricks Build the First Enterprise AI Platform?
- How to Build a Better Machine Learning Pipeline
- Confluent Reveals ksqlDB, a Streaming Database Built on Kafka
- 10 Big Data Trends to Watch in 2019
- Kafka Transforming Into 'Event Streaming Database'
- Why Every Python Developer Will Love Ray
- Why Knowledge Graphs Are Foundational to Artificial Intelligence
- Is Hadoop Officially Dead?
- More Features…
Most Read News In Brief
- California's New Data Privacy Law Takes Effect in 2020
- Global DataSphere to Hit 175 Zettabytes by 2025, IDC Says
- Mobile Coding is a Thing
- Microsoft Aims for Data Analytics Unification with 'Synapse'
- War Unfolding for Control of Elasticsearch
- HPE Acquires MapR
- Machine Learning Market Demonstrates Solid Growth
- Why Gartner Dropped Big Data Off the Hype Curve
- Intel Debuts New VPU Chip at AI Summit
- Inside Fortnite's Massive Data Analytics Pipeline
- More News In Brief…
Most Read This Just In
- Igneous DataProtect Now Supports Google Cloud Platform Storage
- Informatica Introduces Data Engineering Solution
- Huwei Announces Data infrastructure Strategy and the Open Sourcing of its Data Virtualization Engine HetuEngine
- AWS Announces Nine New Compute and Networking Innovations for Amazon EC2
- TigerGraph Selected to Strengthen Fraud Detection and Credit Risk Assessment
- CockroachDB 19.2 Enables Enterprise to Build Global Applications with Strong Performance
- Striim Announces Incremental Data Capture from Google Cloud Spanner
- Wejo selects Databricks' Analtyics Platform to Help Create a Mobility Data Ecosystem
- Snowflake Launches Private Data Exchange
- Alluxio Announces Advanced Cloud Service Integrations on Amazon AWS and Google Cloud
- More This Just In…
January 26, 2020 - January 28, 2020Austin TX United States