Topic
DORA
4 entries filed under this topic
Data Governance — behaviour with evidence, not policy on paper
Data governance is a set of decisions about data plus the evidence those decisions are being lived — not paper. Cordata's operating-model half of the Fabric + Mesh Hybrid, with the DORA shift that changed personal accountability, federated computational governance as the answer, and the DACH hooks (BaFin § 25b, Betriebsrat, DSGVO Art. 28-30) it has to survive.
Data Engineering — the Fabric + Mesh Hybrid
Data platforms fail for two correlated reasons — organizational and technical. The Fabric + Mesh Hybrid closes both. Cordata's reference architecture and its DACH-specific hooks (DORA, BaFin, FINMA, works-council).
Behaviour-first governance in practice — generating artefacts from platform events
The Data Governance pillar established the concept: artefacts are byproducts of behaviour, not deliverables in themselves. This post walks the four mechanisms that make it real — RoPA from lineage, RACI from catalog ownership, audit report from subscription log, and a change-authorisation workflow where the commit is the evidence. Real Terraform, SQL, and YAML throughout.
Fabric + Mesh on AWS — LakeFormation, DataZone, and one governance plane
The DataEng pillar named the compositional choice but left the code unwalked. Here it is in Terraform: central governance account, per-domain producer accounts, LF-tag-based grants, DataZone publishing in two layers — plus the trap of running two catalog planes over the same data, and three DACH compliance checkpoints hit on the way.