You know, I'm pretty sure you could build a PHP monolith in 2023 without a framework and it would do what it needed to do.
Bad coding is infinitely worse than a “bad” language. I don’t know how many of you are musicians, but many people are surprised to find that the tone quality of a guitar has way more to do with the person playing it than the way it was built.
Monoliths are not dinosaurs
31–40 of 243 posts
Re: Monoliths are not dinosaurs
#32Can't we all just go back? Seriously every system I've worked on in the last 10 years seems worse in every metric than what I worked on 2000-2010.
It's only natural that a job that used to take 2 now takes 10 people because of those facts.
And I agree. We've traded safety and a few other things that could have been ironed out in exchange of massive gridlocks, headaches and colossal facepalms. Performance is only on par if you consider the hardware improvements, it's crazy.
Re: Monoliths are not dinosaurs
#33Can't we all just go back? Seriously every system I've worked on in the last 10 years seems worse in every metric than what I worked on 2000-2010.
DHH has a couple of posts on the topic recently: https://world.hey.com/dhh/how-to-recover-from-microservices-...
Re: Monoliths are not dinosaurs
#34You know, I'm pretty sure you could build a PHP monolith in 2023 without a framework and it would do what it needed to do.
Re: Monoliths are not dinosaurs
#35Can't we all just go back? Seriously every system I've worked on in the last 10 years seems worse in every metric than what I worked on 2000-2010.
Agree. Very few systems benefit from the increased complexity and decreased productivity. DHH has a couple of posts on the topic recently: https://world.hey.com/dhh/how-to-recover-from-microservices-...
Re: Monoliths are not dinosaurs
#36Earlier quoted context omitted.
Agree. Very few systems benefit from the increased complexity and decreased productivity. DHH has a couple of posts on the topic recently: https://world.hey.com/dhh/how-to-recover-from-microservices-...
Rare case of DHH being cogent, I wonder if this was a result of him rediscovering Traefik and Docker Swarm?
Re: Monoliths are not dinosaurs
#37"Complexity can neither be created nor destroyed, only moved somewhere else."
The drive to simplify is virtuous, but often people are blind to the complexity that it adds.
Okay, so your microservices are each very simple, but that made the interactions and resource provisioning very complex. What was the net gain?
The correct solution depends on the circumstances. There are excellent uses of microservices. There are excellent uses of monoliths. There are excellent uses of monorepos. There are excellent uses of ... (wait never mind monorepos are just better).
Understand what is ESSENTIAL complexity and what is INCIDENTAL complexity. Simplify your system to remove as much incidental complexity as possible, until you are left with the essential and be satisfied with that.
Re: Monoliths are not dinosaurs
#38Re: Monoliths are not dinosaurs
#39You know, I'm pretty sure you could build a PHP monolith in 2023 without a framework and it would do what it needed to do.
Re: Monoliths are not dinosaurs
#40You know, I'm pretty sure you could build a PHP monolith in 2023 without a framework and it would do what it needed to do.
Now that PHP has lost its massive deployment advantage, step up to Rails or Python.