God’s Architecture. How-to.

KyivAndroidDevClub #12. November 11 2017

Transcript

1. God’s Architecture. How-to. Alexandr Voronsky Mobile Software Engineer Team Lead, KaaIoT
2. class SuperActivity : NotSuperActivity(), SuperView { fun createAwesomeUi() { ... } fun doFastRestCall() { ... } fun changeAllSingletonsState() { ... } fun justMakeYouFeelPainWithTests() { ... } override fun universalProblemSolver() { ... } }
3. S.O.L.I.D.
4. Single responsibility
5. class SocketReader { fun read(bytes: ByteArray) { ... } private fun getMessageType(): MessageType { ... } private fun write(bytes: ByteArray) { ... } }
6. Open-closed
7. open class SocketReader { init { createBaseReader() } open fun createBaseReader() { ... } fun makeSocketFast() { ... } }
8. Liskov substitution
9. open class Bird { open fun setLocation(x: Int, y: Int) { ... } open fun setAltitude(z: Int) { ... } } class Penguin : Bird() { // Sorry, mister, but I can't fly // Check your inheritance, setAltitude() is USELESS }
10. Interface segregation
11. class Plane : Transport { override fun fly() { /* Flying */ } override fun ride() { /* Riding */ } } class Cab : Transport { override fun fly() { /* Can't fly */ } override fun ride() { /* Riding */ } }
12. Dependency inversion
13. interface Transport class Plane : Transport class Cab : Transport fun addTransport(machines: List<Plane>) { ... } fun addTransport(machines: List<Cab>) { ... } fun addTransport(machines: List<Transport>) { ... }
14. This wall is unbreakable like your faith in rules
15. How it relates to software architecture?
16. MVC/MVP/MVVM
17. MVP: - Presenters are so fat - Sometimes business logic migrates to Presenters MVC: - Relationship between View and Model - Not enough to use in real Android life MVVM: - Brings VM overhead for complex solutions - Android DataBinding is a bad way
18. V for Vendetta VIPER
19. - Independent and robust modules - High percent of test coverage - Great abstractions - Easy for maintaining and extending - Code is really clear as it possible - Uncle Bob is happy +
20. – - A lot of time to implement - A lot of code files - Communication is ugly - Not reusable modules
21. - Truth - MVP/MVC/MVVM - UBER Engineering - Architecture patterns in a nutshell - SOLID - Your best friend
22. Thanks QA