Tetap Agile dengan Arsitektur Monolith - Ziya El Arief
- 1. Replace Me! (Bisa ditambahkan dengan image yang relevan) Tetap Agile dengan Arsitektur Monolith? Ziya El Arief - Product Engineer Dicoding Indonesia
- 2. Marty Cagan At Hewlett-Packard ● 1980 was an engineer in HP ● One of the industry's best technology companies ● They work hard for delivering one great product ● What can be wrong?
- 4. Just one problem: No one bought it.
- 5. Lessons from Marty Cagan ● At least, half of our ideas are just not going to work. ● It typically takes several iterations to get the implementation of this idea to the point where it delivers the necessary business value.
- 6. Agile Agile is an iterative approach to project management and software development that helps teams deliver value to their customers faster and with fewer headaches. Instead of betting everything on a "big bang" launch, an agile team delivers work in small, but consumable, increments. Requirements, plans, and results are evaluated continuously so teams have a natural mechanism for responding to change quickly. https://www.atlassian.com/agile
- 7. Agile Agile is an iterative approach to project management and software development that helps teams deliver value to their customers faster and with fewer headaches. Instead of betting everything on a "big bang" launch, an agile team delivers work in small, but consumable, increments. Requirements, plans, and results are evaluated continuously so teams have a natural mechanism for responding to change quickly. https://www.atlassian.com/agile
- 8. Ga cukup SDLC aja yang Agile, Software Development juga harus Agile.
- 9. Small App
- 11. Agile With Microservices ● Loosely Coupled ● Less Headache ● Iterate Faster ● etc.
- 12. Dicoding ● Small team, 7 Engineers ● A Big Application ○ 42++ Domains ○ 657++ Actions / Controllers ○ 400k++ users
- 13. Monolith ● Simple Deployment ● Simple Refactoring ● Simple Transaction
- 14. Monolith
- 15. But if we are not careful, this can happens
- 16. How to avoid this?
- 17. Introducing the Majestic Monolith
- 19. Monolith Modules
- 23. Bounded Context
- 24. Can be fatty Tightly Coupled Multiple Reasons To Change Conflict Alert Bounded Context
- 27. DRY Principle
- 28. Coding Fun Fact: Reading VS Writing
- 29. 80 : 20 Coding Fun Fact: Reading VS Writing
- 30. Lets Optimize This 🔥 80 : 20 Coding Fun Fact: Reading VS Writing
- 31. Demo Time!
- 34. Developers, when change something in their code
- 35. Make Changes Without Worry with TDD
- 36. TDD 1. Create Acceptance Scenario a. Specify Positive Flow b. Specify Negative Flow 2. Create a test for the first negative case 3. Run test 4. Fail 5. Solve test until success 6. Move to the next test 7. If All negative cases have done, move to the positive cases
- 37. Why TDD not DDT ? ● Memaksa kita untuk membuat object yang mudah diuji ● Focus solving one problem at a time ● More empathy to business rules ● Fail Fast
- 38. Summary ● Karena perubahan itu adalah suatu hal yang pasti maka kode kita harus bisa responsif terhadap perubahan. ● Majestic Monolith menggabungkan kesederhanaan monolit dengan struktur dan fokus dari microservices. ● Prinsip-prinsip Clean Code dapat membantu kita untuk membangun software dengan lebih cepat. ● TDD membantu kita untuk lebih tenang ketika melakukan perubahan sehingga kita bisa tidur lebih nyenyak dan hidup lebih sehat.
- 39. References ● Inspired by Marty Cagan ● Domain Driven Development by Chris Evans ● Clean Code by Robert Cecil Martin ● The Majestic Monolith by David Heinemeier Hansson ● Majestic Modular Monoliths by Axel Fontaine ● https://www.artstation.com/artwork/nQoNAK ● https://thestorybookstore.com/wp-content/uploads/2019/12/Inspired-How-to-Create-Tech -Products-Customers-Love-Marty-Cagan.jpg ● https://lukashajdu.com/img/majestic-modular-monolith/monolith-percaption.png