Алексей Сахаров "Акторная модель программирования в Microsoft Orleans"

Акторная модель — это подход для организации параллельных вычислений, позволяющий улучшить инкапсуляцию и сегрегировать ответственность. Разработчики применяют акторные модели, чтобы сделать приложение пригодным для горизонтального масштабирования при нагрузках. Расскажу как они работают на примере Microsoft Orleans, их плюсы и минусы.

Transcript

1. The Actor model
 &
 Microsoft Orleans Alexei Sakharov Team Lead @ MERA
2. Agenda Microsof t Orleans The Actor model
3. The Actor model
4. The Actor model • Mathematical model of concurrent computation • Actor • Message
5. The Actor model • Scalability • Parallel computing • Transienty between parallelisms • local • global
6. The Actor model • Method call • Do something • Shared memory • OOP • – Obje ct • Receive message • Do somethin g • No shared memory •Actor mode l – Actor
7. The Actor model • Create more actors • Send message to other actors • Decide what to do with the next message (change state) •Receive messag e
8. The Actor model STATE ADDRES S
9. The Actor model • No shared state • Internal state (shared nothing) • Fire-and- forget • Asynchrono us • Lightwei ght process • 1 message – 1 actor • Fault- tolerance • Distributio n
10. The Actor model Development of online-games Equipment management Simulation modeling Pipeline data/transaction processing
11. The Actor model Erlang Elixir Scala
12. The Actor model • .NET • Microsoft Orleans • Akka.NET • PostSharp • JAVA • Akka • Jetlang • Actor • Actr • Python • Pykka • Pulsar • JavaScript • NAct • Vert.x • Comedy
13. Microsoft Orleans
14. Microsoft Orleans - Overview
15. Microsoft Orleans - Overview • Framework • Build distributed high-scale computing applications • No need to learn and apply complex concurrency or other scaling patterns
16. Microsoft Orleans - Overview
17. Microsoft Orleans - Overview
18. Microsoft Orleans - Overview
19. Microsoft Orleans - Overview GRAIN = ACTOR (VIRTUAL ACTOR)
20. Microsoft Orleans - Benefits • Familiar OOP paradigm • Single- threaded execution of grains • Transparent activation • Location transparency • Integration with persistent store • Automatic propagation of errors
21. Microsoft Orleans - Core Concepts Grain Silo Client Cluste r
22. Microsoft Orleans - Grains Active in memory Deactivatin g Persisted Activating
23. Microsoft Orleans - Grains • long • GUID • string • GUID + string • long + string
24. Microsoft Orleans - Grains
25. Microsoft Orleans - Grains
26. Microsoft Orleans - Grains
27. Microsoft Orleans - Grains Days Minutes Hour s Minute s Second s Timers Reminders
28. Microsoft Orleans - Grains • Request Context Observabl e (actor) Observer (actor) Observer (actor) Observer (client) Reentranc y
29. Microsoft Orleans - Grains • Memory Grain Storage • Azure Table Storage • Azure Blob Storage • Dynamo DB • ADO.NET • SQL Server • MySQL/MariaDB • PostgreSQL • Oracle
30. Microsoft Orleans - Grains • Tasks • Intercepto rs • Incoming Call Filters • Silo-wide • Per-grain • Outgoing Call Filters • Grain Services • Stateless Worker Grains • Transactio ns
31. Microsoft Orleans - Grain Prefer local Random
32. Microsoft Orleans - Silo, Cluster & Clients
33. Microsoft Orleans - Silo, Cluster & Clients
34. Microsoft Orleans - Silo, Cluster & Clients Cluster ID Service ID
35. Microsoft Orleans - Silo, Cluster & Clients Handler counters of activity • receiving a method call • receiving a reminder • receiving an event • via streaming Doens't handled counter of activity • performing a call (to another grain or to an Orleans client) • timer events • arbitrary IO operations or external calls not involving Orleans framework
36. Microsoft Orleans - Silo, Cluster & Clients • Serialization • Immutability • Runtime Monitoring
37. Microsoft Orleans - Deployment • Azure Web Apps + Azure Cloud Services • Docker • Service Fabric • Multi- Cluster Supp ort
38. Microsoft Orleans - Hints • Avoid chatty interfaces between grains • Avoid bottleneck grains • Use TPL & await • Use smaller grains (or based on app domain model) • Use timer to re-read state • Use unit tests
39. Thank you for attention! Q/A