Upgrade to Pro — share decks privately, control downloads, hide ads and more …

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

Sebastian Heuer
May 10, 2016
Technology
0
71

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

Sebastian Heuer

May 10, 2016
Tweet

More Decks by Sebastian Heuer

See All by Sebastian Heuer
The State of Asynchronous PHP
sebastianheuer
0
29
Typescript - A Marriage Counselor for Frontend and Backend
sebastianheuer
0
33
The Myth of Untestable Code
sebastianheuer
0
23
Deployment without the Hassle @ IPC 2016
sebastianheuer
1
48
99% is not enough
sebastianheuer
0
92
Don't Fear the Walking Dead - How to get rid of a zombie
sebastianheuer
0
100
A Developer's Survival Guide for the Microservice Era
sebastianheuer
2
380
PHPUGHH - Deployment with OS Packages
sebastianheuer
0
73
How to manage your Project's Toolchain in 2016
sebastianheuer
1
43

Other Decks in Technology

See All in Technology
隣接領域をBeyondするFinatextのエンジニア組織設計 / beyond-engineering-areas
stajima
1
280
スクラムチームを立ち上げる〜チーム開発で得られたもの・得られなかったもの〜
ohnoeight
2
350
Oracle Cloud Infrastructure データベース・クラウド：各バージョンのサポート期間
oracle4engineer
PRO
28
13k
BLADE: An Attempt to Automate Penetration Testing Using Autonomous AI Agents
bbrbbq
0
310
iOS/Androidで同じUI体験をネ イティブで作成する際に気をつ けたい落とし穴
fumiyasac0921
1
110
AWS Lambda のトラブルシュートをしていて思うこと
kazzpapa3
2
180
リンクアンドモチベーション ソフトウェアエンジニア向け紹介資料 / Introduction to Link and Motivation for Software Engineers
lmi
4
300k
個人でもIAM Identity Centerを使おう!(アクセス管理編)
ryder472
3
210
信頼性に挑む中で拡張できる・得られる１人のスキルセットとは？
ken5scal
2
530
Why does continuous profiling matter to developers? #appdevelopercon
salaboy
0
190
IBC 2024 動画技術関連レポート / IBC 2024 Report
cyberagentdevelopers
PRO
0
110
Amplify Gen2 Deep Dive / バックエンドの型をいかにしてフロントエンドへ伝えるか #TSKaigi #TSKaigiKansai #AWSAmplifyJP
tacck
PRO
0
380

Featured

See All Featured
A Tale of Four Properties
chriscoyier
156
23k
For a Future-Friendly Web
brad_frost
175
9.4k
Adopting Sorbet at Scale
ufuk
73
9.1k
The Straight Up "How To Draw Better" Workshop
denniskardys
232
140k
Why You Should Never Use an ORM
jnunemaker
PRO
54
9.1k
RailsConf 2023
tenderlove
29
900
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
131
33k
Templates, Plugins, & Blocks: Oh My! Creating the theme that thinks of everything
marktimemedia
26
2.1k
A designer walks into a library…
pauljervisheath
204
24k
Happy Clients
brianwarren
98
6.7k
How to Ace a Technical Interview
jacobian
276
23k
Helping Users Find Their Own Way: Creating Modern Search Experiences
danielanewman
29
2.3k

Transcript

  1. HOW WE GET RID OF OUR MONOLITH DON’T

  2. None
  3. None
  4. None

  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

  13. None
  14. None

  15. FURY Frontend Key-Value Storage getCategoryPage(341); "<html><head>…</head><body>…</body></html>"

  16. None

  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 [email protected] http://www.kartenmacherei.de/recruiting