Marcin Grzejszczak, Łukasz Szczęsny
Microservices are the top buzzword in IT recently. Rarely people think that it’s not just about having a separate codebase for each service. Even if you produce that fat jar from your code what happens now? How does your deployment pipeline look like? Having a microservice based architecure implies heavy impact on the infrastructure and its automatic provisioning. Distributed systems need to have their logs and metrics aggregated.
No more fixed ports and addresses definitions. Do you actually know what service discovery means? If you haven’t thought about this then you shouldn’t go the microservice way. We will explain what microservices are, why they are not that trivial to deal with and how to automatically set up the infrastructure around them.