Distributed systems have been around for a while. Since like 1970s we’ve been building applications with large scale in mind, and large availability. We went even more in that direction since the Internet Bubble around ‘95 and we still carry on. Then, at the beginning of 2010s, the microservices happened. “Fine grained SOA", how Adrian Cockcroft, former director for the Cloud Systems at Netflix described them, took over the development world.
It is impossible nowadays to not hear about microservices. It’s so “buzzy” word that everyone is talking, writing and thinking about it – either developers and managers. In this blogpost I’d like to focus on some useful cases concerning Python & Microservices altogether.
In today buzzword-oriented world, you don’t spend all of your precious time following all of the latest technologies. When creating APIs, you rarely think twice - obviously REST is your best friend. But have you ever heard about companies like Google or Dropbox? I bet you did. They’ve considered this problem in a different way. So did we, in our last project for a Berlin startup. We decided to use gRPC instead of REST and I would like to tell you why.
The microservices architecture is definitely one of such trendy solutions that is widely considered, especially in new projects. Is it worth trying and what kind of advantages and drawbacks does it have? Let’s see.