Don't start with microservices – monoliths are your friend
There is a lot of talk about monoliths vs microservices lately.. I just want to throw into the ring that you can do both at the same time. easily. And noone is going to kill you for it either.<p>maybe we are getting caught up in sematics because its christmas, but &quot;monorepo&#x2F;monolith&#x2F;microservices&#x2F;etc&quot; is -just- the way you organize your code.<p>Developing a montolith for years but now you have written a 15 line golang http api that converts pdfs to stardust and put it into on a dedicted server in your office? welp thats a microservice.<p>Did you write a 150 repo application that can not be deployed seperatly anyway? welp thats a monolith.<p>You can also build a microservice ecosystem without kubernetes on your local network. We have done it for years with virtual machines. Software defined networking just makes things more elegant.<p>So dont stop using microservices because its &quot;hard&quot; or start writing monoliths because its &quot;easy&quot;, because none of that is true in the long run.<p>What is true is that you have a group of people trying to code for a common goal. The way you reach that goal together defines how you organize your code.