Data engineering
Data contracts & schema governance
A schema registry and an enforcement point, so a producer cannot break a consumer silently.
4–8 weeksTypical duration
The problem this solves
A team changes a field, three dashboards break a week later, and the conversation is about blame rather than about contracts.
What you receive
Artefacts you can hold, and that you can accept or refuse — never a list of activities.
- A schema registry with compatibility rules chosen per subject
- Contract enforcement in the pipeline, so an incompatible change fails at the producer
- A change process that makes a breaking change visible before it ships
- The ownership map, naming a person per dataset
Also in data engineering
Lakehouse foundation
An open-table-format estate with the catalogue, the layout, the compaction and the retention decided rather than defaulted.
Streaming backbone
A Kafka and structured-streaming spine with exactly-once semantics, checkpointing and replay, built so a late record has a defined fate.
Batch-to-streaming conversion
An existing nightly estate turned incremental without a rewrite, one pipeline at a time.