Just developing software is not enough. You’ll need to get it on production and you want to be sure that you deploy quality software and not breaking software. In this article, part of our microservices journey, I’ll describe how we have set up our deployment pipeline in a way that developers can do their own deployment complying to our standards. Continue reading
Following up on the previous blog posts on our move to a microservices architecture, this time I want to dive into how to actually manage the transition from monolith to microservices. It may seem like a daunting task, but as with anything big and scary, you’ll find it to be less so once you start bringing it down to a more manageable size. The keyword after all, is micro. Let’s get started!
In our first blog describing our microservices journey, Victor went over our reasons to move to a microservices architecture. In this article I’ll describe how we started development on our first microservices and making some upfront decisions on technology.
Before we dive into microservices, first a little history lesson on Coolblue’s system architecture and how it has developed itself through the years. This should give you an idea of the landscape we’re dealing with, what challenges were facing and how we believe we can overcome them.