A pattern language for microservices
I have been doing microservices for 4 years now and I can tell you something: do not go there. The tools are simply not there.<p>Although I am working on one platform like that right now (see <a href="https:&#x2F;&#x2F;github.com&#x2F;1backend&#x2F;1backend" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;1backend&#x2F;1backend</a>) the reason I started it was more the fact that I could not easily deploy a custom tiny service and call it easily.<p>We have solved both problem with 1Backend: launching a new service is as easy as creating a git repo on GitHub, and calling them is just like calling a library with the autogenerated clients.<p>That being said, until a project like 1Backend matures, anyone who starts their startup on a microservices architecture instead of a simple monolitic one is out of their skull.*<p>I have personally watched millions and millions of dollars burnt on building on such platform while our competitor (Uber) became one of the biggest unicorns the world has ever seen.<p>Don&#x27;t be that startup! We managed to screw it up with 100+ million dollars in funding, which was (is) extremely exceptional in Europe. Of course the tech was only part of the reason for failure, still: there are better way of spending money than chasing bugs across hundreds of services and building instrumentation.<p>*Edit: this sentence of mine was very unfortunately worded and said the exact opposite of what I meant. Hopefully the tons of upvotes I got was because that the upvoters correctly inferred from the context that I advice you to start with a monolith, and not with microservices. Thanks.