Don't fear the Walking Dead @ IPC 2016
•
1 like•707 views
Revised talk held by Sebastian Thoß and Sebastian Heuer at International PHP Conference 2016 in Munich. "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."
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Don't fear the Walking Dead @ IPC 2016
Similar to Don't fear the Walking Dead @ IPC 2016 (20)
More from tech.kartenmacherei
Recently uploaded
Recently uploaded (20)
Don't fear the Walking Dead @ IPC 2016
- 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
- 15. Our Initial Setup Legacy System Session Storage RDBMS Webserver PIM / ERP Cache
- 21. FURY Frontend Key-Value Store ["SBU06HE","TEOD3HE","ANW04HD"] Search search("{'category':'hochzeit', 'filters':{}}"); getTiles(["SBU06HE","TEOD3HE","ANW04HD"]); ["<div class="category-item">…</div>", …]
- 22. CQRS-based Architecture PHP Frontend Session Storage Webserver Key/Value Store PHP Backend PIM / ERPSearch Engine
- 23. Incoming Request PHP Frontend Session Storage Webserver Key/Value Store PHP Backend PIM / ERPSearch Engine
- 24. New Data PHP Frontend Session Storage Webserver Key/Value Store PHP Backend PIM / ERPSearch Engine
- 25. Webserver Key-Value Store Search FURY Frontend FURY Backend FURY Components
- 26. Webserver Key-Value Store Search FURY Frontend FURY Backend Legacy RDBMS Legacy System Session Storage Collect & Export K-V Store
- 27. Webserver Key-Value Store Search FURY Frontend FURY Backend Legacy RDBMS Legacy System FURY Requests 200OK Session Storage K-V Store
- 28. Webserver Key-Value Store Search FURY Frontend FURY Backend Legacy RDBMS Legacy System Requests to Legacy System 404NOTFOUND Session Storage K-V Store
- 29. Webserver Key-Value Store Search FURY Frontend FURY Backend Legacy RDBMS Legacy System Requests to Legacy System 404NOTFOUND 200 OK Session Storage K-V Store
- 30. Learnings • we have full responsibility now • no framework needed • no relational database needed • accessing the legacy session storage was too slow • solved by adding a read slave for FURY
- 31. Goods and Bads • three months of development until first launch • fully object-oriented • easy refactoring thanks to 100% code coverage • not enough automated acceptance tests • dependencies to legacy software (database changes, API calls)
- 32. A/B Deployment
- 33. Webserver (Router) Webserver FURY Frontend Server A K/V StoreSearch FURY Backend Webserver FURY Frontend Server B K/V StoreSearch FURY Backend
- 34. Webserver (Router) Webserver FURY Frontend Server A K/V StoreSearch FURY Backend Webserver FURY Frontend Server B K/V StoreSearch FURY Backend active = A
- 35. Webserver (Router) Webserver FURY Frontend Server A K/V StoreSearch FURY Backend Webserver FURY Frontend Server B K/V StoreSearch FURY Backend active = B
- 36. Webserver (Router) Webserver FURY Frontend Server A K/V StoreSearch FURY Backend active = B
- 37. RDBMS Read Slave Webserver FURY Frontend Server A K/V StoreSearch FURY Backend Webserver (Router) Build Server Deploy Code active = B
- 38. RDBMS Read Slave Webserver FURY Frontend Server A K/V StoreSearch FURY Backend Webserver (Router) Build Server Deploy Code Collect & Export active = B
- 39. RDBMS Read Slave Webserver FURY Frontend Server A K/V StoreSearch FURY Backend Webserver (Router) Build Server Deploy Code Collect & Export Smoke Tests active = B
- 40. Smoke Tests<?php namespace KartenmachereiIPC2016; use PHPUnit_Framework_TestCase; class SmokeTest extends PHPUnit_Framework_TestCase { /** * @dataProvider furyUrlProvider * * @param Url $url */ public function testFuryUrl(Url $url) { $result = $this->sendGetRequest($url); $this->assertSame(200, $result->getStatusCode()); $this->assertNotEmpty($result->getBody()); $this->assertLessThanOrEqual(100, $result->getTimeToFirstByteInMilliseconds()); }
- 41. RDBMS Read Slave Webserver FURY Frontend Server A K/V StoreSearch FURY Backend Webserver (Router) Build Server Deploy Code Collect & Export Smoke Tests active = B
- 42. RDBMS Read Slave Webserver FURY Frontend Server A K/V StoreSearch FURY Backend Webserver (Router) Build Server Deploy Code Collect & Export Smoke Tests active = B
- 43. RDBMS Read Slave Webserver FURY Frontend Server A K/V StoreSearch FURY Backend Webserver (Router) Build Server Deploy Code Collect & Export Smoke Tests Switch to A active = A
- 44. RDBMS Read Slave Webserver FURY Frontend Server A K/V StoreSearch FURY Backend active = B Webserver (Router) Build Server Deploy Code Collect & Export
- 45. What's next?
- 46. Client /product
- 50. Next steps • open-source our CQRS RESTful Framework • replace the next parts of the legacy system with new, self-contained components / services
- 52. Next steps • open-source our CQRS RESTful Framework • improve our deployment process • replace the next parts of the legacy system with new, self-contained components / services
- 54. Next steps • open-source our CQRS RESTful Framework • improve our deployment process • replace the next parts of the legacy system with new, self-contained components / services
- 55. "one hundred fifty-seven quinvigintillion, seven hundred eighty-six quattuorvigintillion, six hundred fifty-seven trevigintillion, seven hundred forty-seven duovigintillion, three hundred forty unvigintillion, one hundred eighty-six vigintillion, (…) nine hundred forty-five quintillion, eight hundred twenty-eight quadrillion, two hundred seventy trillion, eighty billion, …"