I recently published the code behind the event-driven reactive programming examples on the Composed System Bitbucket page under the project name Stream.  Stream is open source and if you are interested in collaborating on it let me know.  Because the source code is now being hosted in a public repository I am going to remove the VIP from the Tools page on this blog, that VIP is already out of date so go to the Bitbucket page and get the latest version.

I've spent the last few posts talking about decoupling actors using event driven architecture (EDA).  Now that we have a common vocabulary I want to show some code that practices what I've been preaching.  So I decided to take the CLD ATM sample exam twice, writing one solution as a queue driven producer consumer and the other as an EDA actor system using event streams to drive the application.  Let's take a look at both.

My last post discussed the different types of coupling between actors in a data-centric event-driven application.  This post will follow up with a deeper look at semantic coupling in these data-centric event-driven applications and I will propose a way to loosen this type of coupling.