Category Archives: EDA

Talk – Putting your events on a diet

Last night I did a talk on event design in service oriented architectures with the abstract. A common problem when designing service oriented architectures is that events going across services tend to be very large in terms of properties they carry. This has the negative effect of making development tougher, testing harder and deployment a [...]

Also posted in SOA | Comments closed

Don’t assume message ordering

On my travels I often see people getting into trouble by assuming that messages will be processed in the same order as they are being sent. If the there was a list of fallacies for asynchronous messaging this one would be: Messages will always be processed in order The reason why this is not true mainly comes from the [...]

Also posted in Guidelines, Messaging, Queuing | Comments closed

Not all events are created equal

No, this post has nothing to do with the declaration of independence but perhaps that we need to design our events with a little more independence in mind. Events denotes important things that has occurred in our business. These events are useful for things like keeping persistent view models updated in a CQRS architecture and as way to communicate between [...]

Also posted in DDD, SOA, SOA 2.0 | Comments closed

>Messaging matters!

> As a part of the Certified Architect course we where required to write an IT-related paper to get our exam. Inspired by Udi Dahans article on autonomous services I decided to write a paper on how the choice of messaging patterns between services in an Service Oriented Architecture (SOA) highly affects key quality attributes [...]

Also posted in ESB, SOA | Comments closed