Benefits And Downsides Of Microservices
What are the benefits of microservices and why are they becoming so popular with large brands like Netflix?
The main benefit of microservices is to allow a large team of engineers to development software more quickly. It’s not for everyone, though.
Companies work hard to deliver value to the world through software. Sometimes there is a breakaway success. When that happens, the stampede of new users can overwhelm the development team. So the company adds new developers to the project to handle the demand.
A lot of people start to work on the same code base and that works for a while. But, over time, problems start to appear. Software builds take several minutes or even hours. Flaky tests waste a lot of debugging time. Releases are fragile and stressful to deploy.
Microservices are one of the answers to these problems. That is why they are so popular with large companies like Netflix, Amazon, and Google.
These companies know that their products will have millions of users on day one. So they know they need the infrastructure in place to handle huge product growth without slowing the team down.
That is why projects created in these companies are increasingly using this architecture from the first days of development.
Are smaller companies seeing the same benefits? Do microservices bring the same benefits to small scale projects with small teams?
The companies that benefit from microservices are those that need to innovate quickly and are planning to grow their development team past 10 engineers or so.
On the other hand, companies with products that rarely change would probably not see any benefit from microservices.
Also, teams with less than 10 engineers or so can probably get away with working on the same code base, without microservices, if the team has good communication.
Microservices reduces the need for constant human-to-human coordination. Unsurprisingly, microservices work really well for teams spread around multiple time-zones, independently of company size.
What are the downsides to using microservices with smaller teams?
Smaller teams should be very careful when planning to move to microservices. It can take a lot of time and effort to make it work, and that effort is often better spent working on other projects.
Engineers often share horror stories about botched attempts to move to microservices that fail because:
- they got the design wrong;
- migrating to the new infrastructure takes forever;
- they can’t hire people with the right kind of experience to execute the project.
The last challenge is the most significant for smaller companies.
How to make a successful transition to microservices?
The key for small teams to effectively move to microservices is to aim for simplicity and be realistic that it could fail. Start small, with one simple service, and assume you will get the design wrong the first time. Limit the amount of time spent on the new project and do not stall other initiatives on the team.
Once you have a good base for building up other services, and that it is not wasting people’s time with bugs, add new projects to it. Slowly transition the team’s development time to the new infrastructure, and eventually, stop working on the old code base. Leave it running forever if it is not causing problems.
About Yves Junqueira
Yves was a Site Reliability Engineer at Google for almost 10 years. Now he is working on an open-source project to build a fast-track for software development teams.
Stay up to date with the
lastest news from Yourbase.io
Other Articles You Might Like
To move fast, software development teams should use small independently-released microservices. But how small should...read more
In my last article, we covered how the software monolith is the result of a successful software project that delivers...read more
I left Google 3 months ago after almost ten years there. I am now building on a fast track for software development...read more