Microservices

So now we now that software needs to be designed in a simple way trying to keep functionalities decoupled so it's easier to maintain, extend, detect and solve bugs. Let's think about a big website, Youtube. What would happen if the whole architecture of Youtube had its whole codebase on a single service? A single mistake whether it's someone that made a small mistake and an exception was thrown or they forgot to pay electricity (I know this wouldn't happen but stay with me) would bring the whole server down. It's obviously not manageable and scalable, this is why microservices where made to make a more modular architecture. Whether we need to make an update to the service or application, or only fix it, the process of implementing the changes is far easier than it used to be, as we can see there are many advantages and benefits of using this new and trending type of architecture and in this entry we are going to talk more about how microservices work and my perspective as a software developer.

Basically, microservices allow us to deploy parts of any system individually, as I mentioned this before this is because of the modularity that we can bring with the microservices architecture, thanks to the deployment of the individual parts the full deployment of the application is done far simpler because at the end we will be able to make changes without the need of updating the entire application.

Overall, I think that the microservices architecture is a great tool for every system or platform that is made nowadays and well. Currently, I have been working with microservices for over 9 months and I can definitely say they do tend to make work a lot easier, but even more importantly, it helps to keep your software scalable.