In the 'What are microservices (part 3)' we touched different approaches to building a microservices architecture. In this final post of series on microservices, I will discuss those approaches in more details.
When it comes to microservices, the million dollar question is: “How do I decompose my monolith into microservices?”. Well, as you can imagine this can be done in many ways, and here I will be suggesting some guidelines.
I'm an Integration Consultant and part of Infomentum's wider integration team. As well as being a MuleSoft trainer, I'm a certified MuleSoft developer and an Oracle SOA suite specialist.
I’m going to pick up from last week’s post when we discussed the microservices definition, and looked at the alternative approach to microservices, aka the monolith. Make sure you read that before carrying on with this post.
Why is the microservices approach different? Let’s explore the main features one by one.
The discussion on microservices has exploded recently. It’s been heralded as the future. But is it really so new, or something more familiar than we think?
Well, let’s start by setting the scene; what are microservices?
Author: Natalia Bazanova
Whether you have physical shops or not, your website is considered another shopfront, and customers will treat it that way. If you can't find something in a shop, you ask a sales assistant. But what about if you can’t find something on a businesses website? There's often no online shop assistant to ask for help. That's where your customers will turn to a powerful search function to find out what they need from you.