A simple way to improvise pub/sub messaging in an early prototype when you don't want to pull in a full message queueing system is to publish a timeline of even

A simple way to improvise pub/sub messaging in an early prototype when you don't want to pull in a full message queueing system is to publish a timeline of events in an RSS feed. The drawback is that when the system grows, you run the risk of going for the lazy default of keeping RSS publishing of events, and now you need to re-implement large portions of a message queueing system to achieve desired reliability of the RSS feed.