Overview

Our accelerator is Rockdata's reusable Azure data platform for client teams that want a repeatable path from ingestion to governed medallion-style data products.

::: callout note Use the platform lens in the header to switch between Databricks-specific and Fabric-specific implementation notes. Shared guidance remains visible in both modes. :::

Mission and scope

The framework exists to reduce the time it takes to stand up a production-ready Azure data platform.

Infrastructure is defined through reusable templates and automation rather than portal-first setup.
Data contracts drive ingestion, validation, and downstream table behavior.
Client-specific behavior stays in the example implementations or downstream repositories.
Most teams configure and extend the platform through databricks_example/.

Contract-first operating model

Our accelerator is designed around data contracts as the primary control surface for ingestion and downstream table behavior.

Start with the Rockdata data contract hub at datacontracts.rockdata.nl when you need to understand a source model before changing code.
Use the contract definition to confirm schema shape, validation expectations, and downstream behavior before editing notebooks, connectors, or Silver logic.

Platform model

Our accelerator combines a shared platform foundation with two implementation lenses.

Rockdata maintains the reusable platform foundation that handles contract-driven ingestion, medallion processing, and platform integration.
Client teams work in the example implementation for their target platform, where environment values, notebooks, jobs, and contracts are configured.
The platform lens in this documentation shows the parts that differ between Databricks and Fabric.

Core building blocks

databricks_example/ is the main Databricks reference implementation for contracts, notebooks, jobs, and environment configuration.
datacontracts.rockdata.nl is the primary place to inspect source models and contract intent before changing platform behavior.

Who this helps

Platform engineers use the framework to provision repeatable client environments with consistent RBAC, storage, and deployment wiring.
Data engineers use it to move from contracts to ingestion and Silver validation without rebuilding core plumbing.
Analysts and delivery leads use it to understand the platform model, the contract-first workflow, and the boundaries of each layer.

Documentation map

Getting Started explains the fastest route from clone to working environment.
Architecture covers medallion layers, orchestration boundaries, and platform shape.
Infra Plane covers provisioning, identities, storage, and deployment concerns.
Data Plane focuses on ingestion, Bronze, Silver, and hard deletions.
Operations covers monitoring, data quality, troubleshooting, and run-time recovery.
Tutorials provides guided workflows for common scenarios.
Guidelines captures engineering standards and authoring rules.
Reference maps modules and responsibilities.
Examples shows practical implementation patterns.
FAQ captures high-friction answers in one place.

Mission and scope​

Contract-first operating model​

Platform model​

Core building blocks​

Who this helps​

Documentation map​

Recommended reading order​