DevCoach 157 : Back-End | Mendesain Aplikasi dengan Clean Architecture

Transcript

2. Mendesain Aplikasi dengan Clean Architecture Arsy Opraza Akma Curriculum Developer Back-End
3. Agenda • Mengenal Architecture Pattern • Mengenal Clean Architecture • Implementasi Clean Architecture Back-End
4. Sulit ga sih bikin sebuah software? 🤔 Ga sulit kalo sekedar bikin software 🙏
5. Back-End Software yang ideal itu … Software was invented to be “soft.” It was intended to be a way to easily change the behavior of machines
6. Back-End Design Pattern Architecture Pattern VS
7. Back-End Design Architecture
8. Back-End Design Architecture
9. • Testability: Software gampang di-test. • Maintainability: Software gampang di-manage. • Scalability: Software gampang di-scale. • Flexibility: Flexible ketika bisnis berubah. Kenapa software architecture penting? Back-End
10. Architecture Pattern Back-End
11. Architecture Pattern Architectural Pattern lebih berfokus pada separation of concern (soc), yaitu pembagian tugas yang lebih jelas antar komponennya. Tujuan utama dari architecture adalah mendukung siklus hidup perangkat lunak. Back-End
12. Jenis Architecture Back-End Hexagonal source source Onion • DCI • BCE • more…
13. Beragam arsitektur memiliki prinsip yang serupa. Back-End
14. Prinsip Architecture Pattern • Independent of Framework • Testable • Independent of UI • Independent of Database • Independent of External Back-End
15. Clean Architecture Back-End
16. Apa itu Clean Architecture? Clean Architecture adalah software architecture yang berfokus untuk mengenkapsulasi logika bisnis dari framework atau teknologi luar. Back-End
17. Layer Clean Architecture Back-End
18. Enterprise Business Rules An entity can be an object with methods, or it can be a set of data structures and functions. Back-End
19. Application Business Rules These use cases orchestrate the flow of data to and from the entities, and direct those entities to use their enterprise wide business rules to achieve the goals of the use case. Back-End
20. Interface Adapters The software in this layer convert data for the use cases and entities, to the format most convenient for some external agency such as the Database or the Web Back-End
21. Framework and Drivers Frameworks and tools such as the Database, the Web Framework, etc. Back-End
22. The Dependency Rule Dependency hanya boleh terjadi dari arah luar ke dalam. Lingkaran dalam tidak bisa mengetahui apa pun yang ada di lingkaran luarnya. Bagian dalam tidak bisa mengetahui apa pun yang ada di lingkaran luar. Back-End
23. Clean Architecture di REST API • Entities • Use Cases • Repository • Database dan HTTP Server Back-End
24. Alur implementasi API Back-End
25. Crossing Boundaries Back-End Flow aplikasi ga harus berurutan, kita bisa melewati batasnya dengan menggunakan Dependency Inversion Principle (DIP).
26. Dependency Inversion Back-End "High-level modules should not depend on low-level modules. Both should depend on abstractions." (Robert Cecil Martin)
27. Tantangan Clean Architecture • Membutuhkan waktu diawal pengembangan • Learning curve • Overengineering Back-End
28. Thank You arasopraza aras@dicoding.com arasopraza Back-End arsyopraza
29. Feedback! Hadiah: • 1 Token Langganan Academy (30 Hari) *untuk pengisi feedback terpilih! dicoding.id/devcoachfeedback