Atom for Event-Driven Systems

Skip to end of metadata
Go to start of metadata
  • trade scalability for latency
  • inappropriate for very low-latency notifications
  • seconds (or minutes or hours) between events being produced and consumed
  • Suited for many consumers, guaranteed delivery, but latency-tolerant
  • Clients poll the service feed, use caching to reduce workload. Clients responsible for retrieving (inverse of many alternatives)
  • Messages will never arrive out-of-order.
  • Easy to replay entire history.
  • This linking and caching strategy trades efficiency for generalization.
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Apr 03, 2014

    A bonus is that the Atom event-stream is usually quite human-friendly