Microservices

Microservices

To begin with, Martin Fowler et al review what are microservices.

The set-up: Small team developing an App, everything in Git Hub as it should be and working ok. As development grows we have more features, we are also experimenting with ideas, we need to change things. We have a branch for each Sprint, but we also start branching the sprints to play with it. When we push and merge all the branches, we need to make sure everything works again.

Microservices are, in a very simplistic way, independent programs working towards the same goal. Each service is a blackbox with inputs and outputs, each box has its own MVC. All you the service has to be is its job, it does not care what happens with the other ones. There is no core database that needs to be updated. As long as each service works properly, we are happy.

Swift and Microservices: Apple usually does not play ball withother technologies. And since one of the key features of Microservices is that it enables multiple technologies working together. The Netflix development process has been used as the flag bearer of Microservices with different technologies.

However, for me, the key aspect is just speed and modularity, and the ability to grow an app.