architecture
API design for system design interviews
API design for system design interviews. Resources, verbs, pagination, versioning, and a shortener or feed you can write in five minutes.
All categories
Architecture
How services are cut and how work moves between them: monoliths, microservices, events, CQRS and the API in front.
- architecture
Clean architecture for system design interviews
Clean architecture for system design interviews. Dependencies that point inward, a payment cut this way, and when a simpler package layout is enough.
- architecture
CQRS and event sourcing for interviews
CQRS and event sourcing for interviews. Separate write and read models, optional event store, and the lag a read model is allowed.
- architecture
Event driven architecture for interviews
Event driven architecture for interviews. Facts that already happened, consumers you can add later, and when a request-response call is clearer.
- architecture
Microservices vs a monolith in interviews
Microservices vs a monolith in interviews. Independent deploys, the network cost, and when a modular monolith is the honest split.
- architecture
Sagas for distributed transactions, explained
Sagas for distributed transactions, explained. Choreography versus orchestration, compensating steps, and why a saga is not two-phase commit.
- architecture
Stateless services for system design interviews
Stateless services for system design interviews. What the word excludes, where session state lives, and when a stateful service is the honest answer.
- architecture
Stream processing for system design interviews
Stream processing for system design interviews. Event time versus processing time, windows and watermarks, and when a join cannot wait for a batch.