Tag: architecture
API Versioning
1
Strategies for evolving an API without breaking existing consumers — URI versioning, header versioning, and content negotiation.
3mo ago
API Design intermediate
Rules for sizing aggregates correctly — small aggregates with single-entity transactions, referencing other aggregates by ID, and designing boundaries around invariants not convenience.
3mo ago
Architecture advanced
API Composition Pattern
1
An API layer aggregates parallel service calls into a single client response — reducing N round trips to 1 and improving perceived latency.
3mo ago
Architecture advanced
Domain objects with only data (getters/setters) and no behaviour — business logic scattered across service classes.
3mo ago
Code Quality advanced
A translation layer between two systems with different models — preventing a legacy or external system's concepts and terminology from leaking into the domain model.
3mo ago
Architecture advanced
API Design Principles
3
Guidelines for designing interfaces — method signatures, HTTP endpoints, error responses — that are intuitive, consistent, and evolvable.
3mo ago
Architecture intermediate
A single entry point for all clients that handles routing, authentication, rate limiting, and protocol translation for backend services.
3mo ago
Architecture intermediate
Short documents capturing the context, decision, and rationale for significant architectural choices — creating an institutional memory of why the system is built the way it is.
3mo ago
General beginner
The sum of all points where an attacker can try to enter or extract data from a system.
3mo ago
General intermediate