Building easier applications with microservices

Want to know more?

Enter the conversation with Koen!

    Microservices, you may have heard of them. This technology has been on the market for some time, but continues to gain in popularity. What are microservices and why should you use them?

    You could see microservices as a way of developing an application using a collection of smaller services. These services have their own process and are linked via, for example, HTTP. A large monolithic application is in fact broken down into smaller microservices. Why would you do that?


    A major advantage of microservices is the speed with which adjustments can be made. Because you can have different teams working on different parts of an application, communication between developers and product managers can also be more direct.

    Speed in the sense of performance is an important advantage over a conventional monolithic architecture. The microservices structure gives you better insight into parts of an application that perform less well. These are also easier to adapt than in a monolithic structure.

    For the end user, this means in theory a better functioning application with fewer bugs.

    Source: BMC, 2018


    Because the various components communicate with each other using standard protocols, it is possible to write each individual microservice in a different language. This makes it possible to find the right developer for the right component, which leads to a better end result.

    Complexity increases

    If you read the above benefits, you would expect that every application builder would immediately switch to microservices. But there are also some disadvantages.

    Problems can probably be detected and adapted earlier, but with a microservices system, more can actually be broken. There are more moving parts. So the individual parts become simpler, but the total system more complex.

    The use of microservices can also be a pitfall for developers working with traditional systems. If they set up the system as a traditional monolithic system, this can cause problems later on in the development process.

    It will therefore be up to the software developer and the development team whether the use of microservices is of added value.

    Do you want to know more about the use of microservices or do you want to be kept informed about news in the field of software? Then sign up for our newsletter.

    For a look around our office: check our Instagram!