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[...]

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[...]

HTTP might be good enough For many systems there isn’t a need for message queues. Regular HTTP-style request/response are often enough. If your system is architected without thinking about events you might have very little need for it. A webhook can be good enough. It all depends on your architecture and business scenarios if it makes sense. What good is a message queue A message queue is good for dealing with asynchronous messages not expected to be dealt with immediately. You can also use a message q[...]

HTTP might be good enough For many systems there isn’t a need for message queues. Regular HTTP-style request/response are often enough. If your system is architected without thinking about events you might have very little need for it. A webhook can be good enough. It all depends on your architecture and business scenarios if it makes sense. What good is a message queue A message queue is good for dealing with asynchronous messages not expected to be dealt with immediately. You can also use a message q[...]