Forgetting Unity

Clean Architecture and How to apply it to a Unity3D Project

Transcript

1. Forgetting Unity CLEAN ARCHITECTURE APPLIED TO GAMES
2. Code lacking of specific purpose God and Demigod Objects
3. Excessive coupling between systems That reinforces too complex classes with excessive interactions
4. Yerkes-Dodson Law Stress vs performance relation for non-trivial tasks
5. Complex Code Reviews are Ok Cognitive distress promotes static analyser reviews
6. Abuse of certain patterns on tutorials Most of the things are Monobehaviors or scriptable objects Manager classes that do too much Singletons for every system dependency Gameplay mixed with presentation code But people ask on the community for better ways to do it.
7. Why not MVP, MVC, MVVM, Other …? On apps it’s not a discussion point Is there some intrinsic constraint enforced by Unity? Nope Lack of examples of how to decuple your game logic from unity API Fear of producing more complex code for little gain
8. Can TDD be applied to games? On the unit test level for sure if you are well decoupled Also Unity has recently provided a way to do integration testing What for? So that the team don’t fear the refactor Do it well or don’t do it.
9. Let’s try a Clean Architecture
10. The benefits Clear definition of the purpose of the business logic Possibility to defer crucial decisions about dependencies Test friendly code Code reuse Easier to maintain Easier Porting
11. Interactors They implement use cases They are named as verbs Can be implemented as a command pattern, but it’s not a requirement They orchestrate the interaction with the application agnostic rules The input and output data must be plain DTOs
12. Entities Implement the application agnostic business rules They model behaviour not plain data Don’t depend on any code out of the entities layer.
13. Boundaries Provides the required abstractions to decouple the interactors from the other layers. The classes that cross the boundary are also part of the of their definition In a static object oriented language they’re defined as interfaces Interactors implement some boundaries Interactiors implementations may depend on other boundaries
14. Entity Gateways The only other classes that can access the entities. They define the entity provider dependencies as interfaces. Their implementations map an entity definition to the models of external layers.
15. Clean Architecture
16. Not part of clean The presentation layer No 1-1 mappings May use immutable DTOs
17. Common Pitfalls and Issues Pushing data out of the boundary Pushing data into the boundary Anemic Domain Asychronous Boundaries Model Duplication
18. Integrating with Unity Create a monobehavior that initializes the presentation and the core logic Add it to the script execution order before any other script present there Wire the time dependant call to the presentation and the core ( if any ) Your Unity scripts should now only handle representation logic Provide the views access to their viewmodel so they can represent it
19. Contact @Cookingsource References GoogleGroup: clean-code-discussion Architecture: The Lost Years