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
72

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
34
The Myth of Untestable Code
sebastianheuer
0
23
Deployment without the Hassle @ IPC 2016
sebastianheuer
1
48
99% is not enough
sebastianheuer
0
94
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
フロントエンド設計にモブ設計を導入してみた / 20241212_cloudsign_TechFrontMeetup
bengo4com
0
1.9k
Jetpack Composeで始めるServer Cache State
ogaclejapan
2
170
サイバー攻撃を想定したセキュリティガイドライン 策定とASM及びCNAPPの活用方法
syoshie
3
1.2k
alecthomas/kong はいいぞ / kamakura.go#7
fujiwara3
1
300
サービスでLLMを採用したばっかりに振り回され続けたこの一年のあれやこれや
segavvy
2
410
オプトインカメラ：UWB測位を応用したオプトイン型のカメラ計測
matthewlujp
0
170
KubeCon NA 2024 Recap / Running WebAssembly (Wasm) Workloads Side-by-Side with Container Workloads
z63d
1
240
組織に自動テストを書く文化を根付かせる戦略（2024冬版） / Building Automated Test Culture 2024 Winter Edition
twada
PRO
13
3.7k
PHP ユーザのための OpenTelemetry 入門 / phpcon2024-opentelemetry
shin1x1
1
200
Microsoft Azure全冠になってみた ~アレを使い倒した者が試験を制す！？~/Obtained all Microsoft Azure certifications Those who use "that" to the full will win the exam! ?
yuj1osm
2
110
日本版とグローバル版のモバイルアプリ統合の開発の裏側と今後の展望
miichan
1
130
LINE Developersプロダクト(LIFF/LINE Login)におけるフロントエンド開発
lycorptech_jp
PRO
0
120

Featured

See All Featured
A Tale of Four Properties
chriscoyier
157
23k
Building Applications with DynamoDB
mza
91
6.1k
The Illustrated Children's Guide to Kubernetes
chrisshort
48
48k
Embracing the Ebb and Flow
colly
84
4.5k
Raft: Consensus for Rubyists
vanstee
137
6.7k
Save Time (by Creating Custom Rails Generators)
garrettdimon
PRO
28
900
Why Our Code Smells
bkeepers
PRO
335
57k
What's in a price? How to price your products and services
michaelherold
243
12k
How to Think Like a Performance Engineer
csswizardry
22
1.2k
Dealing with People You Can't Stand - Big Design 2015
cassininazir
365
25k
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
132
33k
Fight the Zombie Pattern Library - RWD Summit 2016
marcelosomers
232
17k

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