-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
Implement Actor Model pattern #3232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I'd like to work on this. Planning to use Java's concurrency tools for a basic actor system. |
✅ Implementation Completed Added unit tests for all key classes and verified actual message passing logic. Increased code coverage to 93.9% (from 45.5%). Fixed Spotless formatting violations. Build & tests pass locally via mvn clean install and mvn test. Quality Gate passed on SonarCloud. Please review the PR when you get a chance. I'm happy to make further adjustments if needed! |
✅ Requested Changes Implemented Refactored logging using Lombok’s @slf4j annotation Implemented proper message-passing verification in the unit test (ActorModelTest) Finalized and committed a fully structured README.md following the project format: Includes real-world example, diagrams, benefits/trade-offs, usage, etc. Added working links to references, tutorials, and related patterns 🔁 Kindly review the updates and let me know if any additional changes are needed. Happy to iterate further if required! |
* feat: Implement Actor Model pattern #3232 * feat: Implement Actor Model pattern #3232 * feat: update Actor Model implementation with multi-actor logic #3251 * feat: update Actor Model implementation with multi-actor logic and loose coupling #3251 * test: add unit test for actor model #3251 * test: add test for App.java to increase coverage * docs: add complete README for Actor Model pattern also implemented changes #3251
Description
The Actor Model is a concurrency paradigm in which independent “actors” encapsulate state and behavior, interacting solely through asynchronous message passing. This approach avoids shared mutable state and promotes highly scalable, loosely coupled systems. Actors can create new actors, send messages to other actors, and handle messages they receive.
Key Elements
References
Acceptance Criteria
actor-model
(or similar)..md
file) explaining the pattern, including code walkthrough and any relevant diagrams.The text was updated successfully, but these errors were encountered: