Over the last few years, microservices have gone from an overhyped buzzword to something you should understand as a software engineer.
According to an O’Reilly developer survey in 2020:
These numbers will only continue to increase over time as the ecosystem around microservices matures and makes adoption even easier.
This doesn’t mean you need to be an expert on microservices to get a job, but it is definitely a bonus to at least understand the basic fundamentals.
The truth is, microservices aren’t that hard to understand when you boil it down to the basics. The biggest problem is that most of the resources available are written to impress readers instead of actually educating them.
Another reason is that there isn’t even a true concrete definition about what a microservice is. The result is that there are tons of overlapping definitions and jargon which leads to confusion for people trying to learn about microservices.
In this article I will cut through all the chaff and focus on the core concepts of what microservices actually are. I’ll use a variety of real world examples and metaphors to make abstract concepts and ideas easier to understand.
Here’s what we’ll cover:
If you prefer a quick introduction to microservices, you can watch this video first: