Stateful Services on Service Fabric: Keeping Data Next to the Compute
How Microsoft Service Fabric's reliable collections and replica lifecycle let services own partitioned state instead of pushing every byte to an external database.
Tag
12 articles · 46 min of reading
How Microsoft Service Fabric's reliable collections and replica lifecycle let services own partitioned state instead of pushing every byte to an external database.
How DoorDash extracted its logistics and dispatch systems from a Django monolith first, and built a service platform to avoid microservices sprawl.
Why Slack adopted Envoy as a common proxy layer for internal service traffic, replacing a patchwork of per-service networking logic.
Why Netflix built Conductor, a workflow orchestration engine, to replace scattered state machines buried inside individual microservices.
Airbnb's honest account of splitting its Rails monolith into services, the sprawl it caused, and the platform investment that fixed it.
How the transactional outbox pattern makes updating a database and publishing an event atomic, without a distributed transaction.
The story of Netflix's edge gateway and circuit-breaker library, and why isolating failure mattered more than avoiding it in a microservices fleet.
How an internal Bezos mandate requiring all Amazon teams to expose functionality only through service interfaces set up the conditions for AWS.
How to combine Resilience4j's circuit breaker, bulkhead, and retry modules in Spring Boot without letting them fight each other.
How Uber's Domain-Oriented Microservice Architecture organized thousands of services into gateways and layers after sprawl made the old model unmanageable.
As DoorDash broke apart its Python monolith, it picked Kotlin over Go and plain Java for the new microservices, and ran the cutover service by service.
Choreography versus orchestration, compensating actions, and the eventual consistency you actually get from the saga pattern.