Do You Need a Microservices Architecture?
Do You Need a Microservices Architecture?
Here is a brief overview of the pros and cons of microservice and when they should and should not be used.
Join the DZone community and get the full member experience.
Join For FreeSnapLogic is the leading self-service enterprise-grade integration platform. Download the 2018 GartnerMagic Quadrant for Enterprise iPaaS or play around on the platform, risk free, for 30 days.
Last week I spoke at the Bangalore Software Architects Meetup on the topic "Do you need microservices architecture?". Here is the presentation and bit more info about it.
Over the last few years there has been lot of attention on microservices. After the initial "hype" we saw that which problems it can solve and which it can not. I have tried to cover what are microservices and where they can be useful and where not. I want to share these guidelines which can be used to choose between a monolith and microservices.
I feel that one must answer the below questions before being able to choose a microservices architecture and it will be beneficial to you if the answers to these questions are "YES".
Does your services represents different business cases/domains..?
Does the services needs to be deployed and managed independently..?
Does different parts of the application has different scaling/Technology needs..?
A modular monolith can be transformed to a set of microservices in case the need arises. So, we should start with a monolith when we are not sure about the future.
With SnapLogic’s integration platform you can save millions of dollars, increase integrator productivity by 5X, and reduce integration time to value by 90%. Sign up for our risk-free 30-day trial!
Like This Article? Read More From DZone
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}