Organizing the Raw Zone - Data straight from the Producers

The right approach for laying down raw data in your data lake or your Cloud Warehouse depends on your goals.

  • Are you trying to ensure the data lands exactly as sent for traceability?
  • Are you planning on transforming the data to a consumer model to decouple producers and consumers?
  • Are you have structure, semistructured, documents, or binaries?
  • Do you have PII exposure?


Video


Presentation Slides

This section exists to provide static copies of the material in the video. Additional content may be added over time.

We're talking as if you have a data pipeline that moves data from the producers into locations that are friendly to data consumers.  It could be a simple pipeline with just a couple steps or it could be something sophisticated that includes things like DataVault modeling layers. Two main things to think about. Who owns making the data consumable?  Are you capable of supporting an ongoing promotion process that converts data from producer schemas to consumer schemas?

Some organizations just drop the data in their raw zone for others to directly consume.  The rest of the slides assume that lake or warehouse data goes through one or more transformations to make it more usable by consumers.  

The next decision is to determine if any changes will be applied to incoming data before it is first landed. This decision can be more difficult than it sounds. It takes into account traceability, governance and capabilities.

A raw zone or landing zone strategy must take into account the different shapes and types of data. I've worked at places where our landing strategy only worked for flat or rectangular data.  It was all pretty straightforward and fell short of covering all our data. We had to come back later and design a binary document strategy.  Look at your data to get a feel for the variation.

We just talked about the different types of data.  Each of those data shapes has its own challenges with respect to size, shape, complexity, and data protection.  You may end up with a couple different strategies depending on the structure, size, and data type.  You can design a good system that totally collapses under a few high volume data sets that have occasional large records. Sometimes companies will pick a raw zone strategy that doesn't work with any of the standard tools for those data types.  For example, There are tradeoffs for embedding pictures/images inside other data types.

Watch the video for a discussion of Flat, Rectangular data in the raw zone.  I've also done several other blog articles about rectangular data in a data lake.

Watch the video for a discussion of Document or Nested structure data in the Raw Zone

Watch the video for a discussion of managing Binary data in a Raw Zone

Blog created 2021/12

Comments

Post a Comment

Popular posts from this blog

Installing the RNDIS driver on Windows 11 to use USB Raspberry Pi as network attached

Image
I do a lot of my development and configuration via ssh into my Raspberry Pi Zero over the RNDIS connection. Some models of the Raspberry PIs can be configured with  gadget drivers  that let the Raspberry pi emulate different devices when plugged into computers via USB. My favorite gadget  is the network profile that makes a Raspberry Pi look like an RNDIS-attached network device.  All types of network services travel over an RNDIS device without knowing it is a USB hardware connection. A Raspberry Pi shows up as a Remote NDIS (RNDIS) device when you plug the Pi into a PC or Mac via a USB cable. The gadget  in the Windows Device Manager picture shows this RNDIS Gadget connectivity between a Windows machine and a Raspberry Pi. The Problem Windows 11 and Windows 10 no longer auto-installs the RNDIS driver that makes magic happen. Windows recognizes that the Raspberry Pi is some type of generic USB COM device. Manually running W indows Update  or  Upd...
Read more

Understanding your WSL2 RAM and swap - Changing the default 50%-25%

Image
The Windows Subsystem for Linux operates as a virtual machine that can dynamically grow the amount of RAM to a maximum set at startup time.  Microsoft sets a default maximum RAM available to 50% of the physical memory and a swap-space that is 1/4 of the maximum WSL RAM.  You can scale those numbers up or down to allocate more or less RAM to the Linux instance. The first drawing shows the default WSL memory and swap space sizing. The images below show a developer machine that is running a dev environment in WSL2 and Docker Desktop.  Docker Desktop has two of its own WSL modules that need to be accounted for.  You can see that the memory would actually be oversubscribed, 3 x 50% if every VM used its maximum memory.  The actual amount of memory used is significantly smaller allowing every piece to fit. Click to Enlarge The second drawing shows the memory allocation on my 64GB laptop. WSL Linux defaul...
Read more

Almost PaaS Document Parsing with Tika and AWS Elastic Beanstalk

Image
The Apache Tika project provides a  library capable of parsing and extracting data and meta data from over 1000 file types.  Tika is available as a single jar file that can be included inside applications or as a deployable jar file that runs Tika as a standalone service. This blog describes deploying the Tika jar as an auto-scale service in Amazon AWS Elastic Beanstalk.  I selected Elastic Beanstalk because it supports jar based deployments without any real Infrastructure configuration. Elastic Beanstalk auto-scale should take care of scaling up and down for for the number of requests you get. Tika parses documents and extracts their text completely in memory. Tika was deployed for this blog using EC2 t2.micro instances available in the AWS free tier. t2.micro VMs are 1GB which means that you are restricted in document complexity and size. You would size your instances appropriately for your largest documents.   Preconditions An AWS account. AWS ac...
Read more