Cross-Domain Connections

Where this domain touches databases, distributed systems, backends, cloud, delivery, observability and security — and exactly where each of those owns the depth.

Data Engineering and Database Engineering

The seam is the write-ahead log. Almost every mechanism a source database uses to stay correct decides what a pipeline downstream of it is able to promise.

Q · Which parts of database internals does a data engineer genuinely have to understand, and which are somebody else's depth?
Data Engineering and Distributed Systems

A pipeline does not choose its guarantees. It inherits them from the weakest hop, and most pipeline bugs are a distributed-systems property arriving where nobody expected it.

Q · Which distributed-systems guarantees does a data pipeline actually depend on, and what breaks when they do not hold?
Data Engineering and Backend Engineering

The backend produces transactions, events and logs as a side effect of serving users. We are its downstream consumer, and it usually does not know that.

Q · What does a data platform need from the services that produce its data, and what is unreasonable to ask of them?
Data Engineering and Cloud Infrastructure

A data platform is assembled almost entirely from four cloud primitives. Knowing which four, and what each actually charges you for, is most of platform engineering.

Q · Which cloud primitives is a data platform actually built from, and which decisions about them are irreversible?
Data Engineering and DevOps

Transformation code deploys like software. The tables it already wrote do not, and that asymmetry is the whole lesson.

Q · What does it mean to deploy, version and roll back a change when the artefact is not a service but a table full of history?
Data Engineering and Observability

Observability & Performance owns why it is slow. This domain owns whether it is correct, complete and fresh. Different questions, different signals, different toolkits.

Q · Why is monitoring a data platform a different discipline from monitoring a service, and which signals belong to which?
Data Engineering and Security

A pipeline is a machine for making copies. Every copy inherits the original's obligations and none of the mechanisms that were enforcing them.

Q · What changes about access, classification, retention and deletion once data leaves the system that was protecting it?