Empires fall: Decentralize your code to avoid total collapse

When architecting a distributed system, it’s easy to get caught up in the excitement of all the cloud backend services available to us. Azure Service Bus! AWS Lambda! CosmosDB! We spend a lot of time decoupling all our backend with microservices, each with their own responsibility and stack and so forth, that we often forget: the front-end has to talk to all of these services. But it can be decomposed into components just as easily as the back-end services can. Here’s a story of how we did it.
Read moreIt would be easy to hit a maximum message size when using other message queues as well. Amazon SQS, Azure Queues, and MSMQ all have hard limits on size too. RabbitMQ is one notable message queue that does not have a limit, but even then, the larger your messages become, the worse a RabbitMQ system will perform.
A few weeks ago, Roy Cornelissen and I left for London to speak at the first ever “All about NServiceBus”-conference: NSBCon 2014. Coincidentally it was also a first time I would be attending a conference, ever! Needless to say, I was pretty excited…
Read moreWhen using integration events and asynchronous communication between bounded contexts, it doesn’t necessarily mean a SOA or using a service bus. This communication could also be based on any type of event-bus that can be implemented using different infrastructure technologies.
Read more