| ▲ | cryo32 3 hours ago | |||||||||||||||||||||||||
You can do both with microservices! | ||||||||||||||||||||||||||
| ▲ | mystifyingpoi an hour ago | parent | next [-] | |||||||||||||||||||||||||
I 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. | ||||||||||||||||||||||||||
| ||||||||||||||||||||||||||
| ▲ | zephen 3 hours ago | parent | prev | next [-] | |||||||||||||||||||||||||
But wait! There's more! For $19.95, you can replace your single single point of failure with multiple single points of failure! | ||||||||||||||||||||||||||
| ||||||||||||||||||||||||||
| ▲ | mohamedkoubaa 2 hours ago | parent | prev | next [-] | |||||||||||||||||||||||||
Please, stop it | ||||||||||||||||||||||||||
| ▲ | DJBunnies 3 hours ago | parent | prev [-] | |||||||||||||||||||||||||
Except 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. | ||||||||||||||||||||||||||
| ||||||||||||||||||||||||||