Brilliant Software Architecture or How to Build Good Software
- 1. BRILLIANT SOFTWARE ARCHITECTURE OR HOW TO BUILD GOOD SOFTWARE
- 2. ME Matthias Gronwald, Technical Director matthias.gronwald@turbinekreuzberg.com 15+ years web developer 10+ years eCommerce (Developement, Technical PM, Technical PO, Solution Architecture, DevOps, Administration, Requirements Engineering, ...)
- 3. Projekttitel 30. Juni 2017 WHAT MAKES GOOD SOFTWARE?
- 4. Projekttitel 30. Juni 2017 Kapitel Well crafted • Needs architecture • Flexible • Robust • Easy to maintain Does exactly what it should do • Application behaviour • Fulfils clients needs What makes good software?
- 6. Projekttitel 30. Juni 2017 Kapitel • Less assumptions more asking • Question complexity • Use cases are fun • Happy path first • Requirements will change — always Requirements
- 7. Projekttitel 30. Juni 2017 BE AGILE
- 8. Projekttitel 30. Juni 2017 Kapitel • Setup agile process • Define release cycles • Scope releases • Involve client early • Also possible for classical projects with fixed deadline and budget Be agile
- 9. Projekttitel 30. Juni 2017 DESIGN FOR CHANGE?
- 10. Projekttitel 30. Juni 2017 Kapitel Don‘t • Premature optimization based on assumptions Do • Split up and modularize Design for change?
- 11. Projekttitel 30. Juni 2017 BE MODULAR
- 12. Projekttitel 30. Juni 2017 Kapitel On application level • Identify subject areas and functional components that could be replaceable • No monolith — implement identified components independent from each other (nearly) • Think Microservices and DDD On code level • Loose coupling • Interfaces • Think SOLID design principles Be modular
- 13. Projekttitel 30. Juni 2017 Kapitel What about dependencies? • Build contracts • JSON Schema • XML Schema • Interfaces • DTOs / Transfer objects
- 14. Projekttitel 30. Juni 2017 BE INCREMENTAL
- 15. Projekttitel 30. Juni 2017 Kapitel • Do not head for the best solution that would fit all possible future problems you are going to expect • Head for the best solution you can come up for your current problem • Adapt and extend only when needed • Evolving order principle / less is more • Do Spikes if you are unsure about some implementation approach Be incremental
- 16. Projekttitel 30. Juni 2017 TEST ALL THE THINGS
- 17. Projekttitel 30. Juni 2017 Kapitel • Tests are the key to flexible and robust Software • Increase the maturity in your Software • Enables possibility to change things • Add layer of security • Also for legacy code • Try to practice Test Driven Development Test all the things
- 18. Projekttitel 30. Juni 2017 BUILD PIPELINE
- 19. Projekttitel 30. Juni 2017 Kapitel • Enables regular automated testing • Provides metrics on code quality • Continuous integration • Increases software quality Build Pipeline
- 20. Projekttitel 30. Juni 2017 GREAT POSSIBILITIES
- 21. Projekttitel 30. Juni 2017 Kapitel • Experience of more than 5 decades of software development available in books, papers, talks etc. • Exciting technologies and tools (VMs, Containers, Frameworks) only recently • Now starts the time to write good software Great possibilities
- 23. Projekttitel 30. Juni 2017 Kapitel • Requirements change constantly • It needs an agile process to deal with that • We need to follow a modular approach to software • Tests enable change • No tests without a pipeline • So many possibilities — No excuses anymore Summary
- 24. Projekttitel 30. Juni 2017 MUITO OBRIGADO
- 25. Turbine Kreuzberg GmbH Ohlauer Straße 43 10999 Berlin MUITO OBRIGADO Contact matthias.gronwald@turbinekreuzberg.com Book recommendations • Clean Code by Robert „Uncle Bob“ C. Martin • Code Complete: A Practical Handbook of Software Construction by Steve McDonnell • The Pragmatic Programmer by Andrew Hunt, David Thomas and Ward Cunningham