Platforms treat data as a first-class citizen¶
An internal developer platform should not treat data as an output that appears after application delivery.
Direction¶
Platform capabilities should allow teams to declare and automate:
- data-product metadata;
- ownership and semantic context;
- contracts and compatibility expectations;
- policy and access intent;
- quality and observability expectations;
- provisioning and lifecycle;
- evidence and provenance.
The platform should provide paved roads without becoming a central bottleneck.
Boundary¶
A portal, infrastructure layer or deployment engine can be valuable without constituting the whole platform.
The architecture should distinguish intent and control, delivery and reconciliation, and runtime execution rather than assuming one tool owns all three.
Join the argument
Agree, challenge or add evidence
Architecture improves when its assumptions are challenged. Say which kind of contribution you're making:
- Challenge I disagree because…
- Evidence We've seen this too…
- Question How would this work when…?
- Alternative Another way to approach this…
- Extension This also implies…
Please keep clients, employers and colleagues unidentifiable. Strong contributions may be quoted and credited on this site. Read the contribution guidelines and the privacy notice.
Comments are provided by giscus and stored on GitHub. Posting requires a GitHub account.