chaospatterns@lemmy.world to Programming@programming.devEnglish · 1 month agoLogging Sucks - A review of challenges with loggingloggingsucks.comexternal-linkmessage-square12linkfedilinkarrow-up1135arrow-down10
arrow-up1135arrow-down1external-linkLogging Sucks - A review of challenges with loggingloggingsucks.comchaospatterns@lemmy.world to Programming@programming.devEnglish · 1 month agomessage-square12linkfedilink
minus-squareMonkderVierte@lemmy.ziplinkfedilinkarrow-up17arrow-down2·1 month ago Today, a single user request might touch 15 services, 3 databases, 2 caches, and a message queue. And is the user experience any better?
minus-squareFishFace@piefed.sociallinkfedilinkEnglisharrow-up11·1 month agoProbably yes, because such an aggressively architected system probably serves millions of users and would fall over if it were simpler. Not to say nothing is ever too complicated but there is a valid reason why these things exist
minus-squarePushButton@lemmy.worldlinkfedilinkarrow-up9·1 month agoAdd docker, kubernetes, open telemetry, Prometheus, paperduty, and grafana so that your 5 users can scale your TODO crud app like they deserve! We all know that’s the only viable way to build a software in 2026.
minus-squarecr1cket@sopuli.xyzlinkfedilinkarrow-up4arrow-down1·1 month agoOf course not. But the shareholder value!
And is the user experience any better?
Probably yes, because such an aggressively architected system probably serves millions of users and would fall over if it were simpler.
Not to say nothing is ever too complicated but there is a valid reason why these things exist
Add docker, kubernetes, open telemetry, Prometheus, paperduty, and grafana so that your 5 users can scale your TODO crud app like they deserve!
We all know that’s the only viable way to build a software in 2026.
Of course not. But the shareholder value!