kymr
commented
5 years ago Identity
- why
Type1 / Type2 Decisions
- Type1 Decisions
- Appropriate Coupling
- Consider "thin" auto-generated clients with bi-directional communication and minimize code reuse across service boundaries
- Synchronous & Asynchronous
- If most of your APIs fit the Request/Response pattern, consider a synchronous request handler with nonblocking I/O
- Data Architecture
- Isolate Data from the Service. At the very least, ensure that data sources are accessed via a layer of abstraction, so that it leaves room for extension later.
- Type2 Decisions
- choose a path
- experiment
- iterate
Evolvability
- Evolutionary Architecture
- Define Fitness Functions
Link