Don't Fear the Walking Dead @ PHPUGHH
•
3 recomendaciones•1,096 vistas
Legacy software can be like a zombie: it somehow still works, but nobody would consider it alive and well anymore and the thought of having to touch it makes you want to run away. So what can you do to get rid of it? We are currently replacing our monolithic e-commerce platform with a shiny new custom-tailored solution and want to show you what we do and what we have already learned.
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Similar a Don't Fear the Walking Dead @ PHPUGHH
Similar a Don't Fear the Walking Dead @ PHPUGHH (20)
Más de tech.kartenmacherei
Más de tech.kartenmacherei (8)
Último
Último (20)
Don't Fear the Walking Dead @ PHPUGHH
- 1. HOW WE GET RID OF OUR MONOLITH DON’T
- 3. 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
- 4. 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
- 5. Finding a way out
- 6. You don’t have to replace everything at once!
- 7. What part of the software causes the highest amount of pain? • category pages • product detail pages
- 8. Planning
- 13. FURY Frontend Key-Value Storage getCategoryPage(341); "<html><head>…</head><body>…</body></html>"
- 15. FURY Frontend Key-Value Storage ["SBU06HE","TEOD3HE","ANW04HD"] Search search("{'category':341, 'filters':{...}}"); getTiles(["SBU06HE","TEOD3HE","ANW04HD"]); ["<div class="category-item">…</div>", …]
- 16. Webserver Key-Value Storage Search FURY Frontend FURY Backend FURY Components
- 17. Webserver Key-Value Storage Search FURY Frontend FURY Backend Legacy RDBMS Legacy System Session Storage Collect & Export
- 18. Webserver Key-Value Storage Search FURY Frontend FURY Backend Legacy RDBMS Legacy System Session Storage FURY Requests 200OK
- 19. Webserver Key-Value Storage Search FURY Frontend FURY Backend Legacy RDBMS Legacy System Session Storage Requests to Legacy System 404NOTFOUND
- 20. Webserver Key-Value Storage Search FURY Frontend FURY Backend Legacy RDBMS Legacy System Session Storage Requests to Legacy System 404NOTFOUND 200 OK
- 21. Learnings • We have full responsibility now • No framework needed • No relational database needed
- 22. 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)
- 23. Deployment
- 24. Webserver (Router) Webserver FURY Frontend Server A K/V Storage Search FURY Backend Webserver FURY Frontend Server B K/V Storage Search FURY Backend
- 25. 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
- 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 active = B
- 27. RDBMS Read Slave Webserver FURY Frontend Server A K/V Storage Search FURY Backend Webserver (Router) Build Server Deploy Code active = B
- 28. RDBMS Read Slave Webserver FURY Frontend Server A K/V Storage Search FURY Backend Webserver (Router) Build Server Deploy Code Collect & Export active = B
- 29. 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
- 30. 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
- 31. RDBMS Read Slave Webserver FURY Frontend Server A K/V Storage Search FURY Backend active = B Webserver (Router) Build Server Deploy Code Collect & Export
- 32. We are very close to launch!
- 33. 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
- 34. https://www.instagram.com/kartenmacherei/ Q&A https://www.facebook.com/kartenmacherei/ +49 40 468996861 jobs@kartenmacherei.de http://www.kartenmacherei.de/recruiting