Messages on the Outside, Messages on the Inside

Abstract:

In the classic paper `Data on the Outside versus Data on the Inside` Pat Helland argued that data within a service boundary should be treated differently than data residing outside of it. Here, I shall argue that the same applies to messages. Inside a service boundary messages are tightly coupled to the corresponding data manipulations. Sometimes it is even possible to enforce total order of messages. The moment the message crosses the service boundary, it enters the no man's land where bad things happen. Messages get reordered, duplicated or even lost. Join me in this talk to learn about some patterns you can use to get your messages safely to the other side.

Szymon Pobiega

@SzymonPobiega

Szymon Pobiega used to work on various business software for almost a decade. Of all the ideas and patterns he learnt along the way, asynchronous messaging had the most profound impact. He built his first micro service system in 2010, well before it became fashionable. Over three years ago Szymon quit consulting and joined Particular Software with hope to use his field experience to build tools for developing distributed systems. Szymon is focused, in Particular (pun intended), on message routing patterns and handling of failures. Besides that he enjoys building remotely controlled vehicles with Lego.

Snacks & drinks provided!