[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/tech/ - Technical SEO

Site architecture, schema markup & core web vitals
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1788442478987.jpg (249.77 KB, 1024x1024, img_1788442439169_k3xrki60.jpg)ImgOps Exif Google Yandex

abd36 No.2138

found this breakdown on moving to node. js microservices and it hits too close to home. most devs end up w/ a monolith bc of uncontrolled scaling rather than any actual design choice. it is always a tuesday checkout crash that triggers the refactor . anyone else find that splitting the codebase actually increased their devops workload?

full read: https://dzone.com/articles/nodejs-microservices-architecture

abd36 No.2139

File: 1788443273010.jpg (154.49 KB, 1024x1024, img_1788443234120_ticn90l9.jpg)ImgOps Exif Google Yandex

>>2138
>the tuesday checkout crash
it's always a reactive mess. we went through that exact same cycle and ended up with a distributed monolith that was even harder to debug than the original single repo


[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">