4 ms·
That's exactly why we need to modularize and componentize. We need to reduce dependency, loose the coupling and eliminate side effects. Monolithic is a dead end
by sinuhe69 3y ago
That's exactly why we need to modularize and componentize. We need to reduce dependency, loose the coupling and eliminate side effects. Monolithic is a dead end. Microservices when things get too complex.
- ddejohn 3y ago> Microservices when things get too complex. Microservices are a huge step up in complexity. I'm not convinced monoliths can't be implemented well.
- TremendousJudge 3y agohttps://grugbrain.dev/ https://grugbrain.dev/ has the following to say about microservices: "grug wonder why big brain take hardest problem, factoring system correctly, and introduce network call too seem very confusing to grug"
- klysm 3y agoDoesn't modularization and compartmentalization increase dependency? I'm curious on how you propose we do both at the same time.
- Cthulhu_ 3y agoMicroservices to reduce complexity and coupling is a fallacy. https://riak.com/posts/technical/microservices-please-dont/ https://riak.com/posts/technical/microservices-please-dont/ is a great and succinct counter to all the advantages that microservices claim to have. In summary: > You don’t need to introduce a network boundary as an excuse to write better code > Distributed Transactions are never easy > A bunch of engineers working in isolated codebases leads to ‘Not my problem’ syndrome
- kjkjadksj 3y agoOn the other hand, now there are a couple hundred cryptically named processes running at all times. How many services does Adobe need to run on my computer when I am not actually running their programs? Quite a few as it were.