121–130 of 256 posts
Earlier quoted context omitted.
"grug wonder why big brain take hardest problem, factoring system correctly, and introduce network call too seem very confusing to grug" -- https://grugbrain.dev
There is so much wisdom in here. Fundamentally, don't make life hard for yourself, or others.
The wisdom only applies to the places where it applies, and there is no wisdom there on telling where those places are.
Earlier quoted context omitted.
There is so much wisdom in here. Fundamentally, don't make life hard for yourself, or others.
And yet defaulting into grug-mode is clearly self-defeating. The wisdom only applies to the places where it applies, and there is no wisdom there on telling where those places are.
You don't need a damn network between two pieces of code just to "do one thing and do it well", for God's sake, I'm so sick of this rampant cluelessness in the industry. Do you saturate the resources of one machine and need to split things off? Do you have multiple teams each taking care of their own stuff? Do multiple services, it's fine in those cases. For almost any other reason you are just adding complexity, boi…
This. So much this. We are 5 years into a microservices wank-fest. So far the net ROI is negative, the user experience sucks more than ever, the complexity is so high that people can't get things done, nothing works properly any more and no one owns anything because they have washed their hands of it all. But this is still promoted as a success because no one wants to be accountable for the fuck up. Our team spend mo…
Earlier quoted context omitted.
And yet defaulting into grug-mode is clearly self-defeating. The wisdom only applies to the places where it applies, and there is no wisdom there on telling where those places are.
It's not really. Grug solves problems. Grug does not create problems that need to be solved to solve other problems.
Well, except for the problem of too much grug.
You don't need a damn network between two pieces of code just to "do one thing and do it well", for God's sake, I'm so sick of this rampant cluelessness in the industry. Do you saturate the resources of one machine and need to split things off? Do you have multiple teams each taking care of their own stuff? Do multiple services, it's fine in those cases. For almost any other reason you are just adding complexity, boi…
> If you think that microservices solve the "spaghetti code problem", well, good luck to you, you'll need it. That is a very good point. In fact, good monolithic code layout is a precursor for microservices, as only once you have identified your boundaries and isolated your concerns can you begin splitting them out into their own services. I will say this however - microservices might not solve the "spaghetti code pr…
Earlier quoted context omitted.
Have your teams use façade pattern and you no longer need microservices to "isolate it"
Can your "facade" "isolate" interns making change in your service as well so that the whole service which powers the system doesn't go down. Microservices can.
The WP contact list acted as a shell for all person-to-person communication programs, showing a unified history feed of all communications you can read from a given person. Like RSS but for humans.
It seems like the obvious way to do "lots of small programs" on the phone -- one single place for managing your communication with a person, whether it's Twitter, email, StarCraft, phonecall, chess, WhatsApp, teledildonics, etc.
Earlier quoted context omitted.
Micro services don’t solve any of those either.
What specifically do they not solve? Because in this thread we're, very specifically, discussing isolating the well maintained monolith from risky product produced by consultants, which microservices absolutely do solve.
If hacker news is correct, microservices is the #1 worst idea of software engineering.
And whoever promotes them is either a kid with no experience or a complete moron.
But near the end, there is a gem, which is the introduction of the Hub and Spoke design.
Now Plugin architectures aren't new by any means. But they've not been discussed as much nowadays, and I think the idea of "Hub and Spoke" describes it very well.