3 ms·
You can do both with microservices!
by cryo32 4mo ago
You can do both with microservices!
- zephen 4mo agoBut wait! There's more! For $19.95, you can replace your single single point of failure with multiple single points of failure!
- flawn 4mo agoOr for 100$, get a 5x increase on all failure points - maximum vibes, maximum excitement.
- DJBunnies 4mo agoExcept 9/10 times microservices end up wildly dependent on each other, yielding a distributed monolith. Better to use service oriented architecture and just ship the monolith, you can test easier and skip the extra layers of serialization / deserialization.
- loevborg 4mo agoI think you missed GP's point
- zephen 4mo agoPoe's Law FTW!
- mystifyingpoi 4mo ago> end up So it just happens, right? There is no remedy to this? You know the answer :) BTW I'm all for monolith.
- mohamedkoubaa 4mo agoPlease, stop it
- mystifyingpoi 4mo agoI get the joke, but in ideal world, in microservices, there is no such thing as code duplication across services. As a maintainer of a service, I should not give a crap about code present in some other service - it's some other team's code, why would I care? I don't have to even know that the other team exists. In big systems, it happens that I can't even feasibly know the existence of all the applications.
- cryo32 4mo agoYou mean you don’t have 300 versions of your badly developed rapidly evolving platform services rotting away underneath the bit you didn’t duplicate?
- mystifyingpoi 4mo agoI don't. Other teams - maybe they do, maybe they don't. Who cares, not me. I have responsibility for services of my team, I think we are doing a good job. Being selfish is the core principle of microservice architecture.
- cryo32 4mo agoUntil half your company gets laid off and you have to adopt other people’s shit.
- throwaway2037 4mo agoIn [an] ideal world, in monoliths, there is no such thing as code duplication across subsystems.