Many teams think that breaking the monolith and migrating to microservices will solve all of the coupling and scalability problems we have in our code. This also happened to us and we suffered the most painful parts of microservices, without even having the benefits. After that, we started to develop focusing on decoupling and separation of contexts, but without putting ourselves any infrastructure barrier.

This talk will explain architecture problems suffered at Ulabox, taking into account factors like team size or enterprise objectives, and which is our proposal to evolve our architecture.

Comments

Please login to leave a comment