Clean Architecture
4 likes1,217 views
This document discusses Clean Architecture, an architectural pattern for Android applications. It is designed to be independent of frameworks and UI layers. Clean Architecture aims to follow SOLID principles and the dependency rule, where source code dependencies should only point inward from outer to inner layers. The layers include entities, use cases, interface adapters, and frameworks/drivers. Fernando Cejas' approach to Clean Architecture is also discussed, which uses domain-data-presentation modules with Reactive Programming using RxJava. While this approach has advantages like reusability, it may violate some Clean Architecture principles and has drawbacks like a steep learning curve. Putting the learnings into practice requires addressing issues like dependency on RxJava and over-engineering. More exploration
Clean Architecture
- 2. CLEAN ARCHITECTURE POPULAR ARCHITECTURES IN ANDROID MVP MVVM MVI Clean Architecture VIPER
- 3. CLEAN ARCHITECTURE ARCHITECTURE GOALS Independence from Framework Testable Independent of UI Independent of Database Independent of any external agents (Security, scheduling, etc)
- 4. CLEAN ARCHITECTURE OBJECT ORIENTED DESIGN GOALS S - Single Responsibility Principle O - Open/Closed Principle L - Liskov Substitution Principle I - Interface Segregation Principle D - Dependency Inversion Principle
- 5. CLEAN ARCHITECTURE DEPENDENCY INVERSION PRINCIPLE High-level modules should not depend on low-level modules. Both should depend on abstractions. Abstractions should not depend on details. Details should depend on abstractions.
- 7. CLEAN ARCHITECTURE CLEAN ARCHITECTURE Introduced by Robert C. Martin (AKA Uncle Bob) Inspired by various other architectures like Hexagonal Architecture, Onion Architecture, etc. Readings: https://8thlight.com/blog/uncle-bob/2012/08/13/the- clean-architecture.html https://8thlight.com/blog/uncle-bob/2011/11/22/Clean- Architecture.html
- 8. CLEAN ARCHITECTURE THE DEPENDENCY RULE The outer circles are mechanisms. The inner circles are policies. This rule says that source code dependencies can only point inwards. How? Dependency Injection!
- 9. CLEAN ARCHITECTURE KEY TERMS Entities (Enterprise wide Business Rules or Business Objects of a Single Application) Use Cases (Application Speci鍖c Business Rules) Interface Adapters (Presenters, Controllers, Gateways, etc) Frameworks and Drivers (Android Framework, Web, etc)
- 10. CLEAN ARCHITECTURE IMPLEMENTATION Watch: https://www.youtube.com/watch?v=Nsjsiz2A9mg
- 12. FERNANDO CEJAS APPROACH DATA-DOMAIN-PRESENTER LAYERING Further Reading: https://martinfowler.com/bliki/ PresentationDomainDataLayering.html
- 13. FERNANDO CEJAS APPROACH REACTIVE PROGRAMMING WITH RXJAVA Great for Asynchronous Programming Eliminate Callbacks Robust Error Handling Handles threading
- 14. FERNANDO CEJAS APPROACH REACTIVE CLEAN ARCHITECTURE APPROACH
- 16. ANALYSIS OF FERNANDO CEJAS APPROACH SOURCE CODE https://github.com/android10/Android-CleanArchitecture
- 17. ANALYSIS OF FERNANDO CEJAS APPROACH DOMAIN-DATA-PRESENTATION AS MODULES Advantage: Sharing with multiple android projects Strict separation of dependencies Disadvantage: Navigating between code
- 18. ANALYSIS OF FERNANDO CEJAS APPROACH VIOLATION OF CLEAN ARCHITECTURE PRINCIPLE UseCase knows about scheduling Where should we actually handle scheduling? Some ideas from Android Architecture Blueprint from Google UseCase dependent on RxJava
- 20. PUTTING LEARNINGS INTO PRACTICE ADVANTAGES One level of breakdown for testability Easier to implement functionalities like caching, storage, etc. Reusable Usecases De鍖ning where to add code for speci鍖c functionality Multiple projects can share domain/business logic Implement different presentation patterns like MVVM, MVI, etc.
- 21. PUTTING LEARNINGS INTO PRACTICE DRAWBACKS Dependent on RxJava Boilerplate code UseCaseExecutor takes away several RxJava bene鍖ts Request and Response Models in UseCase Steep learning curve Over-Engineering, perhaps?
- 22. PUTTING LEARNINGS INTO PRACTICE MORE EXPLORATIONS MVP Respository Pattern Dependency Injection with Dagger Testing Consistency in Models
- 23. RESOURCES
- 24. RESOURCES FIVE.AGENCY CLEAN ARCHITECTURE BLOG SERIES Android Architecture: Part 1 Every new beginning is hard Android Architecture: Part 2 Clean Architecture Android Architecture: Part 3 Applying clean architecture on Android
- 26. RESOURCES THE MODEL AND REPOSITORY PATTERN http://hannesdorfmann.com/android/evolution-of-the- repository-pattern http://futurice.com/blog/top-7-tips-for-the-model-in- android-architectures
- 28. TEXT USE CASE SCHEDULING https://medium.com/@yoelglusc/threading-strategies-on- android-with-clean-architecture-57f6d3714d96#.iev6hjyya https://medium.com/@yoelglusc/android-and-clean- architecture-the-use-case- interface-8716512f29a1#.x8gmyvody
- 29. RESOURCES A LARGER EXAMPLE https://github.com/badoo/Chateau
- 30. THANK YOU