single purpose • May be in themselves multithreaded Actors • Isolated, single-threaded components that encapsulate both state and behavior • Can be used to implement microservice environments Amy O’ Leary [email protected] 5
actors • State held by an actor can be thought to be immutable and atomic • In Akka, only one message within an actor is processed at a time, enforcing atomicity [email protected] Amy O’ Leary 7
release small components separately • Single tenancy – easier to trace a fault to a single component • Easier to change resources in a bottleneck component [email protected] Amy O’ Leary 14
designed as actors • Scale up by using Akka Remoting • Any number of actors can occupy their own server • Easy to configure – no code changes needed! • Can combine remoting with routing. [email protected] Amy O’ Leary 17
Error reporting can be vague – no stack trace • Debugging from one actor to another is cumbersome • Still need to learn about concurrency in Java! [email protected] Amy O’ Leary 22
used to manage state in a concurrent system • Akka is a great framework for easily implementing an actor based system • Akka can be easily scaled up to a distributed system [email protected] Amy O’ Leary 24