Don't Fear the Walking Dead - How to get rid of a monolith

Transcript

1. HOW WE GET RID OF OUR MONOLITH DON’T
5. How we started • built on top of a standard e-commerce platform • a lot of custom code to support a wide combination of product options Feature X Feature Y Feature Z Core Code Customization
6. The challenges of a growing business • serious performance issues • own developers don’t feel comfortable with the code • adding individual features is too complex • upgrading is hard
7. Finding a way out
8. You don’t have to replace everything at once!
9. What part of the software causes the highest amount of pain? • category pages • product detail pages
10. Planning
11. Current Setup Legacy System Session Storage RDBMS Webserver
12. Idea Legacy System Session Storage RDBMS Webserver New Software
15. FURY Frontend Key-Value Storage getCategoryPage(341); "<html><head>…</head><body>…</body></html>"
17. FURY Frontend Key-Value Storage ["SBU06HE","TEOD3HE","ANW04HD"] Search search("{'category':341, 'filters':{...}}"); getTiles(["SBU06HE","TEOD3HE","ANW04HD"]); ["<div class="category-item">…</div>", …]
18. Webserver Key-Value Storage Search FURY Frontend FURY Backend FURY Components
19. Webserver Key-Value Storage Search FURY Frontend FURY Backend Legacy RDBMS Legacy System Session Storage Collect & Export
20. Webserver Key-Value Storage Search FURY Frontend FURY Backend Legacy RDBMS Legacy System Session Storage FURY Requests 200 OK
21. Webserver Key-Value Storage Search FURY Frontend FURY Backend Legacy RDBMS Legacy System Session Storage Requests to Legacy System 404 NOT FOUND
22. Webserver Key-Value Storage Search FURY Frontend FURY Backend Legacy RDBMS Legacy System Session Storage Requests to Legacy System 404 NOT FOUND 200 OK
23. Learnings • we have full responsibility now • no framework needed • no relational database needed
24. Goods and Bads • fully object-oriented • easy refactoring thanks to 100% code coverage • not enough automated acceptance tests • dependencies to legacy software (database changes, API calls)
25. Deployment
26. Webserver (Router) Webserver FURY Frontend Server A K/V Storage Search FURY Backend Webserver FURY Frontend Server B K/V Storage Search FURY Backend
27. Webserver (Router) Webserver FURY Frontend Server A K/V Storage Search FURY Backend Webserver FURY Frontend Server B K/V Storage Search FURY Backend active = A
28. Webserver (Router) Webserver FURY Frontend Server A K/V Storage Search FURY Backend Webserver FURY Frontend Server B K/V Storage Search FURY Backend active = B
29. RDBMS Read Slave Webserver FURY Frontend Server A K/V Storage Search FURY Backend Webserver (Router) Build Server Deploy Code active = B
30. RDBMS Read Slave Webserver FURY Frontend Server A K/V Storage Search FURY Backend Webserver (Router) Build Server Deploy Code Collect & Export active = B
31. RDBMS Read Slave Webserver FURY Frontend Server A K/V Storage Search FURY Backend Webserver (Router) Build Server Deploy Code Collect & Export Smoke Tests active = B
32. RDBMS Read Slave Webserver FURY Frontend Server A K/V Storage Search FURY Backend Webserver (Router) Build Server Deploy Code Collect & Export Smoke Tests Switch to A active = A
33. RDBMS Read Slave Webserver FURY Frontend Server A K/V Storage Search FURY Backend active = B Webserver (Router) Build Server Deploy Code Collect & Export
34. We are very close to launch!
35. What next? • party hard! • identify the next pain points we want to work on • replace the next parts of the legacy system with new, self-contained components / services
36. https://www.instagram.com/kartenmacherei/ Q&A https://www.facebook.com/kartenmacherei/ +49 40 468996861 jobs@kartenmacherei.de http://www.kartenmacherei.de/recruiting