> For the complete documentation index, see [llms.txt](https://resources.unizin.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resources.unizin.org/products/data-and-analytics/unizin-data-platform/data-stores/data-lake.md).

# Data lake

<figure><img src="https://3709019308-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKYwtHNGgdPXS3PWAlZUr%2Fuploads%2Fgit-blob-17c3bb6428885deda9259001b8248d5a3f6b5654%2F20448203.png?alt=media&amp;token=58470fdf-648e-4040-87c0-bfa36c16235e" alt="Depiction of the Unizin Data Platform Data Lake"><figcaption></figcaption></figure>

The Unizin Data Platform's [event data pipeline](/products/data-and-analytics/unizin-data-platform/system-overview/event-data-pipeline.md) and [context data pipeline](/products/data-and-analytics/unizin-data-platform/system-overview/context-data-pipeline.md) maintain a data lake that serves as a foundational store for ad hoc inquiry.

The purpose of the UDP Data lake is to act as a comprehensive store for all data imported by a UDP instance for all time. The data lake is composed of two major components:

1. The UDP Context store, which hosts all context data in a single, relational database
2. The UDP Event store, which hosts all event data in a single table

In this section, we cover the design of the UDP data lake and, for Unizin consortium members, document how they can access each in their SaaS implementation.