Learning Akka (Video 17)

This video tutorial covers the implementation of a persistent FSM actor for managing account states. It begins with an introduction to FSM and the account actor, followed by defining states and data. The tutorial then explains domain events and commands, and proceeds to implement the persistent FSM actor by overriding necessary methods. Finally, it defines state handlers and tests the actor, demonstrating its functionality and event replay from the journal.

What are the two states of the account actor?

• Empty and Active

• Inactive and Active

• Empty and Full

• Zero and Non-zero

What is the purpose of defining domain events in the FSM actor?

• To define actor commands

• To handle state transitions

• To represent transaction types and outcomes

• To manage user accounts

Which method is responsible for applying events in the persistent FSM actor?

• updateState

• applyEvent

• handleEvent

• processEvent

What is the role of the persistence ID in the FSM actor?

• To manage state transitions

• To store transaction data

• To identify the actor's state

• To uniquely identify the persistent actor

What happens when a debit operation results in a balance less than zero in the active state?

• The state remains active

• The state changes to empty

• The transaction is accepted

• The transaction is rejected

What is the initial state and data of the FSM actor?

• Active state with positive balance

• Empty state with positive balance

• Empty state with zero balance

• Active state with zero balance

What is the outcome when a credit operation is received in the empty state?

• The state changes to active

• The balance is reset

• The state remains empty

• The transaction is rejected