Microservice architectures are not intended to model complex requirements in large, inflexible, software monoliths characterised by internal dependencies. Instead, these architectures create solutions using large numbers of small, independent modules. These Microservices can be implemented in a polyglot manner, i.e. using the optimum language for each requirement. They communicate with each other using APIs and have a clearly defined scope of functions. Their independence makes them easy to swap out and modify. This flexibility makes Microservice architectures perfect for agile Software Development in distributed DevOps teams and for continuous delivery processes with optimum time-to-market performance.
Complex requirements composed of many small, independent modules.
Many projects contain requirements which can be ideally served using Microservices. Since the initial fundamental concepts of Microservices were first mooted several years ago, we have, therefore, focused very intensively on what we consider to be an extremely sustainable technological concept.
For my master’s thesis I conducted interviews with industry experts in the field of microservice migration. As a result a guidance is provided by thoroughly analyzing the given migration scenarios. It turned out be a crucial point to understand why organizations seek for microservices.
Microservice architecture is one of the buzzwords that has notably influenced software development in recent years. This influence went as far as basically branding the term ‘monolith’ as a bad practice. Monoliths seemingly have to be avoided at all costs and microservices, therefore, appear to be inevitable. That’s why many projects start with this architecture […]
With the Hype around containers and especially Docker many new Linux distributions were created to run containers. Compared to traditional operating systems, there are some benefits when using such a Linux distribution. In this article we compare 5 popular and promising distributions.
