My app went from a single code base that handles a million different actions to a million code bases that each handle a single action, but they still all depend on each other and still are tightly coupled, but now they're spread out across 50 disparate cloud services so maintenance effort only got worse.
this post was submitted on 30 Oct 2025
18 points (69.6% liked)
Programming
23442 readers
136 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
"We can solve any problem by introducing an extra layer of abstraction. Except for the problem of too many layers of abstraction."
Just an ad article. "Did you also encounter skill issues while building web applications? Try my platform."
I'm not an architect, but I do dislike how much of development work has AWS wrangling, dealing with the architectural hoops that are mentioned in the article
When I built Viduli
And there it is. The reason for the whole article.
Article exactly describes how I feel about next.js -ers.
So far none of them was able to explain to me why lack of connection pooling is A good thing. I doubt they even know what that is. If you build a website in server less - you might as well use php because it will beat node.js in raw speed on those conditions and you are handicapping it similarly.
Nah, anyone that pretends BitTorrent is worse than their server-based thing is just foolish