Rethinking Microservices with Orleans
This dotnet session examines how loosely coupled Orleans components can support different deployment layouts without tying application design to physical distribution.
Separating application structure from deployment
Traditional microservice architectures often treat architectural separation and physical distribution as the same problem. Orleans takes a different approach: applications can be implemented as loosely coupled components while their deployment topology remains flexible.
Drawing on experience building game backends and other services, the session explores how an application can evolve through several deployment arrangements without changing its underlying programming model:
- A single process
- Multiple clusters
- Multiple regions
Communication costs and operational trade-offs
The session examines how Orleans can reduce communication costs and simplify operations, while also addressing the realities of latency in globally distributed systems. Flexible deployment does not remove those constraints; latency and communication costs remain considerations when deciding where components should run.
The central design question is whether a logical application boundary also needs to be a physical deployment boundary. Keeping those decisions separate offers a way to reconsider common microservice assumptions as a system’s deployment requirements change.