Interactor
ELI5 — The Vibe Check
An interactor is just another name for a use case — it's the code that 'interacts' with your domain to accomplish one specific task. Some people call them use cases, some call them interactors, some call them application services. Same thing, different LinkedIn profile.
Real Talk
In Clean Architecture terminology, an interactor is an object that encapsulates a single application use case, containing the application-specific business rules. The interactor receives input from the controller (via an input boundary), orchestrates domain objects, and delivers output through an output boundary/presenter.
When You'll Hear This
"The interactor orchestrates the domain objects — the controller just passes in the request." / "Each interactor implements an input boundary interface, making it easy to test in isolation."
Related Terms
Clean Architecture
Clean Architecture is like an onion with strict rules: the inner layers (your core business logic) have absolutely no idea the outer layers (databases, API...
Controller
A controller is the manager who actually handles your request after it passes through security.
Presenter
A presenter takes raw data from your use case and formats it for display.
Use Case
A use case is a single thing a user can do with your system — 'Place Order', 'Register Account', 'Cancel Subscription.