The Application: An Unexpected Journey

Tale of how an application changed from a monolithic architecture to a service-oriented and back again, and why it was necessary.

RubySPB 2013

Transcript

1. The Application An Unexpected Journey
2. Andrey Savchenko @ptico GitHub Twitter LinkedIn Aejis
3. PHASE 1 Monolith
4. Easy to start
5. Easy to start • Fast development
6. Easy to start • Fast development • Simple infrastructure
7. Easy to start • Fast development • Simple infrastructure • Follows the common Rails patterns
8. Hard to grow • Poor scalability
9. Hard to grow • Poor scalability • Low maintainability
10. Hard to grow • Poor scalability • Low maintainability • Testing headache
11. Hard to grow • Poor scalability • Low maintainability • Testing headache • Follows the common Rails patterns
12. PHASE 2 SOA
13. Advantages
14. Advantages • High scalability
15. Advantages • High scalability • Ability to choose different technologies
16. Advantages • High scalability • Ability to choose different technologies • Maintainable codebase
17. Problems
18. Problems • Data synchronization
19. Problems • Data synchronization • Authorization
20. Problems • Data synchronization • Authorization • Testing and deployment
21. Problems • Data synchronization • Authorization • Testing and deployment • Expensive HTTP requests
22. Problems • Data synchronization • Authorization • Testing and deployment • Expensive HTTP requests • Moon in scorpio
23. Bonus: Internet Explorer
24. TIL
25. TIL • Grape suck
26. TIL • Grape suck • ActiveResource suck much more
27. Tools • Vagrant (bonus: rove.io)
28. Tools • Vagrant (bonus: rove.io) • tmux + tmuxinator
29. PHASE 3 Reimagined Monolith
30. Single application + Use cases
31. Combine advantages from the previous two approaches
32. Combine advantages from the previous two approaches • Fast development
33. Combine advantages from the previous two approaches • Fast development • Simple infrastructure
34. Combine advantages from the previous two approaches • Fast development • Simple infrastructure • Easy to maintain
35. Combine advantages from the previous two approaches • Fast development • Simple infrastructure • Easy to maintain • Easy to test and deploy
36. Final thoughts
37. Start as simple as possible
38. Enhance your architecture iteratively
39. Choose right tools
40. Andrey Savchenko @ptico Thanks!