A microservice journey part 5 - dependancies
Moving from a monolith to a microservice Architecture is hard. It is important to understand what are the issues with the monolith before jumping right it. If you understand what your problem is, you can make sure you don't introduce the same problem in a microservice ecco-system. Distributed Monolith When we start realising the benefit of building new things and linking them via an API, it can be quite tempting to make everything a service. The problem starts to arise when one service calls another which calls another. This leads to a bunch of services which are dependent on each other. You end up back to where you started in a monolith like structure, you end up with a distributed monolith. The problem with Monoliths is that everything is accessible. It seems like a good idea at the time, sharing code seems like a no brainier. Usually there is one big catch-all project which contains all the utility type code. Once shared between other parts of code, you can never change i...