Microservices, high availability & architecture review
A review that ends in a ranked list of what will break first, and what it costs to fix each one.
Most architecture reviews produce a diagram. This one produces an order: the failure modes that are actually reachable, ranked by what they cost when they happen, with the cheap mitigations separated from the expensive ones.
The high-availability side comes from years on services where redundancy and concurrency were the product, including Power Query Dataflow at Microsoft and a collision detection engine that ran without a crash in production.
What you get
- Failure modes ranked by cost and reachability, not by severity labels
- Service boundaries assessed against the actual coupling, including the database
- Concurrency, retry and idempotency assumptions checked where they matter
- A document another engineer can execute without me in the room