November 20, 2019
Practical Aspects of Microservice Architecture presented on Code::Dive Nokia organized IT conference
- Michulka R.
In the presentation I will focus on practical consequences affecting system and entity when applying certain solutions as a part of microservice architecture, each design brings benefits, limitations, and risks to the system. I treat each solution as a contract with the system, and I will describe what kind of obligations, requirements, and consequences are to come with it. Microservices are nothing new, the idea is a practical consequence of providing a service. Back in the days of early systems, the same need resulted with Unix Philosophy dogmas which sum up to "Do one thing and do it well". On the system aspect, I would like to focus on how microservice architecture impacts the product life-cycle. How ones need to think about developing, testing, deployment, security as part of feature introduction. How in a distributed environment the security and monitoring capabilities become matters of greater complicity. On the entity aspect, I will discuss the core service features one needs to operate a future-proof service. How the applied pattern or technology can impact the service itself. How the chosen system patterns impact service contract or behavior. How to ensure data consistency and safe rollback of done actions. How each service can apply measures that contribute to overall system self-healing capability.View Original Article