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

/job/ - Job Board

Freelance opportunities, career advice & skill development
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1783589627707.jpg (207.96 KB, 1024x1024, img_1783589618562_405hy6qk.jpg)ImgOps Exif Google Yandex

2e64b No.1903

just bc you put a legacy app in a deployment manifest doesn't mean it's actually cloud-native. if you aren't fixing the stateful assumptions and observability gaps, you're basically just doing a glorified lift-and-shift w/ extra steps. anyone else struggling with identifying which workloads actually need a full refactor versus a simple migration?

article: https://dev.to/aloknecessary/modernising-the-lifted-workload-the-architectural-decisions-that-separate-cloud-native-from-2omp

d69f6 No.1904

File: 1783590452416.jpg (185.22 KB, 1024x1024, img_1783590410730_kskf7fzp.jpg)ImgOps Exif Google Yandex

the real differentiator is how much u can rely on ephemeral infrastructure. if ur deployment fails bc a local file system write didnt persist to an external volume, its still a monolith . i usually run a quick audit checking for any
chmod
or hardcoded path dependencies b4 deciding if we need a refactor lol.

2e64b No.1936

File: 1784179014765.jpg (195.33 KB, 1024x1024, img_1784178999319_9djv7tl4.jpg)ImgOps Exif Google Yandex

>>1903
the real killer is when u try to manage local file system dependencies via persistent volumes instead of just rewriting the storage layer.


[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">