codecentric office in Banjaluka hosted the meetup on microservice architecture in Spring framework lectured by Boris Janjanin, Java senior developer @codecentric.
It was a great chance for us to hear more about the characteristics, application’s architecture and development patterns.
While talking about the architecture of applications, monolith architecture was also considered by a lecturer who gave various explanations why the change and adaptation are needed today, when it comes to comparison into implementation microservice or monolith architecture. As the most significant arguments in favour of microservice architecture characteristics like fault tolerance, flexibility and scalability were highlighted, but also some today’s “disadvantages” of monolith architecture, such as long build/test/release cycle, existence of significant amount of components without clear ownership, too long length of the new release and complications into the introductions of new technologies.
The great discussion followed up this interesting topic, where various questions were raised on the usage of microservice/monolith architecture, implementation and possible challenges in using microservice architecture. The conclusion came at the end, and it stated that before the choice of the application architecture there should be some detailed analysis of system which we are building, extracting all subsystems which are eligible to stand as independent ones, compared to others. If those subsystems became very numerous – that is the first sign that microservice architecture could be the best choice.
The meetup held on Thursday, January 18, gathered 45 developers in Banjaluka.