Microservices are a modern software architecture design where an application is split into many small services allowing teams to innovate faster and achieve massive scale.Learn more about GitLab
Microservices architecture is most commonly understood by comparing it to a legacy "monolith" application architecture. With a monolith, all of the components are part of a single unit. With microservices, each component is broken out and deployed individually as a services. Services communicate with each other via API calls.
With a monolithic application everything is developed, deployed, and scaled together. The app must be written in a single language, with a single runtime. Different teams working on different parts of the app need to coordinate in order to make sure they don't affect each other's work. For example, one part of the app my depend on a module that needs a specific version say 1.8, which another teams needs the same module, but requires the 1.7 version because 1.7 is incompatible with another dependency. In a monolithic app you have to pick one or the other. Similarly, everything is deployed as a single application so code must be tested and deployed together.
While every organization defines microservices differently, Martin Fowler's quintessential article on microservices defines 9 components that most microservice architectures have in commons.
Folwer goes into detail during this talk at GOTO;
Building applications with a microservices architecture, or decomposing a legacy monolith into microservices increases velocity, flexibility, and scalability, at the cost of simplicity. Monoliths are simple to build, deploy, and debug, but are very hard to scale. By using a more complex microservice architecture engineering organizations gain several benefits
While GitLab is great for microservices today, there are several features on the roadmap to make it even better.