Download as PDF, PPTX
![FURY Frontend
Key-Value
Store
["SBU06HE","TEOD3HE","ANW04HD"]
Search
search("{'category':'hochzeit', 'filters':{}}");
getTiles(["SBU06HE","TEOD3HE","ANW04HD"]);
["<div class="category-item">…</div>", …]](https://image.slidesharecdn.com/dontfearthewalkingdead-ipc2016fall-161024142256/75/Don-t-fear-the-Walking-Dead-IPC-2016-21-2048.jpg)
Uploaded bytech.kartenmacherei
Don't fear the Walking Dead @ IPC 2016
The document outlines the challenges of transitioning from a monolithic e-commerce platform with significant custom code to a more sustainable architecture. It details the performance issues faced, such as difficulty in upgrading and complex feature additions, and introduces a strategy for incrementally replacing components while utilizing a CQRS-based architecture. Future steps include open-sourcing their framework and enhancing deployment processes to further replace legacy systems with self-contained components.
More Related Content
Similar to Don't fear the Walking Dead @ IPC 2016
Don't fear the Walking Dead @ IPC 2016
- 1. HOW WE GETRID 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 ofa growing business • serious performance issues • own developers don’t feel comfortable with the code • adding individual features is too complex • upgrading is hard
- 7.
- 8. You don’t haveto replace everything at once!
- 9. What part ofthe software causes the highest amount of pain? • category pages • product detail pages
- 10.
- 11.
- 12.
- 13.
- 14.
- 15. Our Initial Setup LegacySystem Session Storage RDBMS Webserver PIM / ERP Cache
- 16.
- 19.
- 21.
- 22. CQRS-based Architecture PHP Frontend Session Storage WebserverKey/Value Store PHP Backend PIM / ERPSearch Engine
- 23. Incoming Request PHP Frontend Session Storage WebserverKey/Value Store PHP Backend PIM / ERPSearch Engine
- 24. New Data PHP Frontend Session Storage WebserverKey/Value Store PHP Backend PIM / ERPSearch Engine
- 25. Webserver Key-Value Store Search FURY Frontend FURYBackend FURY Components
- 26. Webserver Key-Value Store Search FURY Frontend FURYBackend Legacy RDBMS Legacy System Session Storage Collect & Export K-V Store
- 27. Webserver Key-Value Store Search FURY Frontend FURYBackend Legacy RDBMS Legacy System FURY Requests 200OK Session Storage K-V Store
- 28. Webserver Key-Value Store Search FURY Frontend FURYBackend Legacy RDBMS Legacy System Requests to Legacy System 404NOTFOUND Session Storage K-V Store
- 29. Webserver Key-Value Store Search FURY Frontend FURYBackend Legacy RDBMS Legacy System Requests to Legacy System 404NOTFOUND 200 OK Session Storage K-V Store
- 30. Learnings • we havefull 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.
- 33. Webserver (Router) Webserver FURY Frontend ServerA K/V StoreSearch FURY Backend Webserver FURY Frontend Server B K/V StoreSearch FURY Backend
- 34. Webserver (Router) Webserver FURY Frontend ServerA K/V StoreSearch FURY Backend Webserver FURY Frontend Server B K/V StoreSearch FURY Backend active = A
- 35. Webserver (Router) Webserver FURY Frontend ServerA K/V StoreSearch FURY Backend Webserver FURY Frontend Server B K/V StoreSearch FURY Backend active = B
- 36. Webserver (Router) Webserver FURY Frontend ServerA K/V StoreSearch FURY Backend active = B
- 37. RDBMS Read Slave Webserver FURY Frontend Server A K/VStoreSearch FURY Backend Webserver (Router) Build Server Deploy Code active = B
- 38. RDBMS Read Slave Webserver FURY Frontend Server A K/VStoreSearch FURY Backend Webserver (Router) Build Server Deploy Code Collect & Export active = B
- 39. RDBMS Read Slave Webserver FURY Frontend Server A K/VStoreSearch FURY Backend Webserver (Router) Build Server Deploy Code Collect & Export Smoke Tests active = B
- 40. Smoke Tests<?php namespace KartenmachereiIPC2016; usePHPUnit_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/VStoreSearch FURY Backend Webserver (Router) Build Server Deploy Code Collect & Export Smoke Tests active = B
- 42. RDBMS Read Slave Webserver FURY Frontend Server A K/VStoreSearch FURY Backend Webserver (Router) Build Server Deploy Code Collect & Export Smoke Tests active = B
- 43. RDBMS Read Slave Webserver FURY Frontend Server A K/VStoreSearch 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/VStoreSearch FURY Backend active = B Webserver (Router) Build Server Deploy Code Collect & Export
- 45.
- 46.
- 47.
- 48.
- 49.
- 50. Next steps • open-sourceour CQRS RESTful Framework • replace the next parts of the legacy system with new, self-contained components / services
- 52. Next steps • open-sourceour 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-sourceour 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-sevenquinvigintillion, 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, …"
- 56.