Beyond “Modern” Data Architecture

The current data architecture landscape (often referred to as a “modern” data architecture), which reflects a systems-based approach (and data silos).
  • The data warehouse
  • The data lake
  • The data marts (or serving layer)

Thinking Differently About Data

Over the past couple of years, I’ve noticed that as data architects begin to work with Snowflake, they continue to fall back on that legacy systems–based data architecture design, using Snowflake only as a data warehouse or maybe expanding it a bit to include some data marts. And most continue to argue for maintaining a separate file-based data lake outside of Snowflake, even when building one from the ground up. But why continue to think this way when Snowflake can replace all of these systems?

All enterprise data can be grouped into logical data zones.
Resist the urge to overlay the old systems-based thinking on top of your data zones.
Snowflake Cloud Data Platform allows you to manage all of your enterprise data with one platform.

One Platform For All Enterprise Data

Several names are used today to identify where data is located and how it is used, including operational data store (ODS), corporate information factory (CIF), data warehouse, data mart, and many more. Each term represents a different way to group data within the enterprise. But unfortunately, today those different groups of data represent different data systems. Let’s start thinking about data in terms of zones (or types of data) not as systems.

A modern data architecture design with one data platform to manage all of your workloads.



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Jeremiah Hansen

Jeremiah Hansen


I’m currently a Field CTO Principal Architect at Snowflake. Opinions expressed are solely my own and do not represent the views or opinions of my employer.