Concept
The U Framework concept: complexity inside the framework, simplicity for the developer.
Design draft. The U Framework is a concept in active design. Nothing on this page describes released software.
The problem
A modern application is a small amount of product logic surrounded by a large amount of infrastructure: build pipelines, environments, secrets, CDNs, push delivery, service discovery, API gateways, monitoring and backups. Each is a discipline. Each is re-solved, slightly differently, by almost every team.
The cost is not only time. Infrastructure that is assembled by hand is hard to reason about, hard to secure and hard to hand over.
The idea
Complexity belongs inside the framework. Simplicity belongs to the developer.
U Framework is designed to absorb that recurring infrastructure into a small set of well-defined primitives. A developer states intent — deploy this service, expose this API, push this message — and the framework carries out everything the intent implies, with secure and observable defaults.
Design goals
- Few primitives, composable. Six verbs should cover the infrastructure of most applications. See Primitives.
- Explicit escape hatches. Every abstraction can be opened. Teams can take control of any layer without abandoning the rest.
- Secure and observable by default. Encryption, service authentication, metrics and logs are the starting point.
- Portable. Intent is described independently of a vendor, so systems can run on a VPS, a cloud platform or both.
- Readable. The configuration of a system should be understandable by a new engineer in an afternoon.
Non-goals
- Replacing application frameworks. U Framework sits beneath Next.js, React Native or a Python service, not instead of them.
- Hiding failure. When something goes wrong, the framework should make the cause more visible, not less.
Open questions
- Where exactly should the framework stop and leave control to the developer?
- How should versioned contracts between services be expressed and enforced?
- What is the smallest useful first release?
These questions are tracked as part of the infrastructure research direction.