As with all trending architectures, companies are looking to leverage (specific) benefits before fully understanding the advantages and disadvantages of these solutions. Working with Microservices Architectures is no exception.

Recently we did some research into the intricacies of communications in a microservice architecture, and we want to share our insights with you!

For those who cannot wait for our findings, we are strong believers that asynchronous communication is the way to go. The use of synchronous communication should be limited to only specific use cases. If you want to know how we reached this conclusion you will have to read through the entire blog. But be aware that getting this aspect right in your architecture is crucial as a microservice architecture heavily relies on communication between its components (microservices).

Our debate on choreography vs. orchestration isn’t one to be had at concert halls or ballet recitals. It’s one architects and developers started having in front of whiteboards, when distributed event-driven systems first started appearing.

Micro service architectures come with many new challenges. In this article, we zoom into the challenge of data islands/consistency. You will learn why this problem arises and what it is. We go deeper into what Event Sourcing and CQRS are and how they might solve this problem, if applied correctly.

Before you consider your options in choosing the right database, you should at least know what your options are. In this blog we'll explain you four types of different database and how they can be used in your organization.

For those of you who’ve read Quinten’s previous blogpost about Microservices, know that we already decided on Cassandra as the primary persistence layer of our Microservices architecture. “I do not regret that decision, but I have to admit that I made it without fully understanding the consequences”, Quinten explains.

“Seniors and juniors will always help you out and nobody should be afraid to ask questions. The more you work in team, the more progress you’ll make!”

There’s something satisfying and fascinating about leaning back in your chair and looking back at the blueprint, the architecture of a fully distributed system you’ve brought to life. Let's find out what Quinten has to say about Microservices and the future of IT.