What is a microservice There isn’t a clear definition of microservices architecture unless you pick one persons strongly held beleif. This can mean that what someone considers microservices, someone else considers to be something else. To summarize a few of the available characterizations and definitions: James Levis and Martin Fowler organization around business capability automated deployment intelligence in the endpoints, not the transport decentralized control of languages and data Jimmy[...]

What is a microservice There isn’t a clear definition of microservices architecture unless you pick one persons strongly held beleif. This can mean that what someone considers microservices, someone else considers to be something else. To summarize a few of the available characterizations and definitions: James Levis and Martin Fowler organization around business capability automated deployment intelligence in the endpoints, not the transport decentralized control of languages and data Jimmy[...]

Polyglot I’ve found that I’m way more productive in some languages compared to others. This is common enough occurance according to Thoughtworks that they mention polyglot programming under their tech radar in techniques. It also allows the use of heterogenous teams that can bring different strenghts to the table. Sometimes a language/virtual machine has a library or framework especially suited for your problem/task. Code chunks Shitty code behind nice interfaces If we look at the group intercommun[...]

Polyglot I’ve found that I’m way more productive in some languages compared to others. This is common enough occurance according to Thoughtworks that they mention polyglot programming under their tech radar in techniques. It also allows the use of heterogenous teams that can bring different strenghts to the table. Sometimes a language/virtual machine has a library or framework especially suited for your problem/task. Code chunks Shitty code behind nice interfaces If we look at the group intercommun[...]

Single deployment If the system you are developing is intended to be delivered by a single team (or a single backend team), there might be less need for a decomposed solution where parts can be deployed separately. This also applies if you are starting out on something relatively small and don’t have the operations setup for doing microservices. If you still will want to structure your code in separate parts with clear API boundries between them you can define request/response, publish: /// <summary[...]