Call for round the year submissions for Rootconf in 2020

Microservices architecture style has been a prominent talking points over the last few years. Microservices is by no means a silver bullet though, and the design thinking required to create a good microservices architecture is the same as that needed to create a well-structured monolith. This talk briefly covers characteristics of microservices, monoliths and modular monoliths. We will discuss the topics like, does microservices suits all problem domains? Where does it fails? Can we re-look at the existing styles and look for continual improvements in architectural style?

Outline

Microservices architecture style has been a prominent talking points over the last few years. Microservices is by no means a silver bullet though, and the design thinking required to create a good microservices architecture is the same as that needed to create a well-structured monolith. This talk briefly covers characteristics of microservices, monoliths and modular monoliths. We will discuss the topics like, does microservices suits all problem domains? Where does it fails? Can we re-look at the existing styles and look for continual improvements in architectural style?

A modular monolith or a well-thought combination between software components allow fast development while maintaining low complexity. They also allow evolving to a more appropriate architecture when the need appear since logical modules can easily be extracted into physical modules. By (re)visiting various styles, we will look at the guidelines which can be used to choose between a modular monolith and microservices.

The presentation will start with a brief introduction of microservices and its characteristics. We will see the issues with traditional architecture (or the lack of it commonly referred as big ball of mud architecture). We will discuss the possible improvements to monoliths with better modularity. In my experience modular monoliths can solve most problems related to maintainability and architectural stability of systems. You will need microservices when there is a need for variable scaling requirement in the same problem domain or the interacting systems have different contextual domain boundaries. I will try to explain these concepts with practical use cases which I have observed.

Speaker bio

Manu is a top-notch Team Leader and Architect with the passion and experience to build software products which can solve complex business problems. He is an expert full-stack developer, building products from concept to completion, with a proven track record of delivering powerful, stable,clean and comprehensive solutions.

Links

• http://blog.manupk.com/
• https://youtu.be/xO61JnNRmAs