3 ms·
Monoliths have been around for decades and much smarter people than me have been thinking about this problem. Unfortunately there is just no way to enforce dis
by threeseed 8y ago
Monoliths have been around for decades and much smarter people than me have been thinking about this problem.
Unfortunately there is just no way to enforce discipline because monoliths sometimes demand unintuitive behaviour. Often it is better to cut/paste code than it is to link from one module to another. And don't forget that when a deadline hits developer are often forced to do things that aren't always architecturally sound.
Microservices forces isolation between modules.
- DenisM 8y agoPerhaps I should have said "there should be methods of enforcing discipline". As in, "we should make/find them". In .NET you could compile individual assemblies separately and use technical measures to prevent developers from one component from touching code in the other component. The external surface of the assembly would be its API, only no network traffic is required. Does this give us enough discipline, in your opinion?
- batiste 8y ago> Often it is better to cut/paste Micro service surely put the dream of code sharing to REST. Not sure it is a good thing.