Orleans

• Distributed-Systems-Runtime
• #summary https://learn.microsoft.com/en-us/dotnet/orleans/overview
  • hasHighlight
    • based on Actors
• hasConcept
  • Virtual Actor abstraction
    • represented as Grain
  • Silo
• description: Instead of building a monolith, or a services-based architecture where the services are statically provisioned, it allows you to decompose your application into lots of small, stateful services that can be provisioned dynamically when you need them.

Use Cases

Orleans should be considered when:

• Significant number (hundreds, millions, billions, and even trillions) of loosely coupled entities. To put the number in perspective, Orleans can easily create a grain for every person on Earth in a small cluster, so long as a subset of that total number is active at any point in time.
  • Examples: user profiles, purchase orders, application/game sessions, stocks.
• Entities are small enough to be single-threaded.
  • Example: Determine if the stock should be purchased based on the current price.
• Workload is interactive.
  • Example: request-response, start/monitor/complete.
• More than one server is expected or may be required.
  • Orleans runs on a cluster that is expanded by adding servers to expand the cluster.
• Global coordination is not needed or on a smaller scale between a few entities at a time.
  • Scalability and performance of execution are achieved by parallelizing and distributing a large number of mostly independent tasks with no single point of synchronization.

Examples

• https://learn.microsoft.com/en-us/dotnet/orleans/tutorials-and-samples/

Resources

• https://www.infoq.com/articles/project-orleans-actor-based/

hasLearningResource

• Adventure game sample project | Microsoft Learn
• stack overflow: Orleans slow with minimalistic use case
• Building a realtime server backend using the Orleans Actor system, Dotnet Core and Server-side Redux

---

Children

1. Indexing
2. Silo

---

Backlinks

• Proto.Actor
• Actors