Blog Posts about messaging

Thumbnail: Yuck! Stateless Poison Message Handling

  Jan 30, 2015   |      Dirk Myers

It’s January, and many people (including me) are thinking about the food they’ve eaten over the last few months. If you’ve ever eaten too much Halloween candy, indulged yourself in holiday food that doesn’t quite agree with you, had too many cookies or gone back for that one last sliver...
amps messaging stateless clients

Thumbnail: New Feature: Keep It All Together With CorrelationId

  Feb 9, 2015   |      Dirk Myers

One of the best things about AMPS is the way that it keeps publishers completely independent from subscribers. Publishers don’t need to know how many subscribers are listening for a message, where they are, or even whether they’re connected at a given point in time. That flexibility pays off: once...
amps messaging correlation response routing

Thumbnail: How Fast Can You Go?

  Feb 18, 2015   |      Joy Vincent

AMPS is built from the ground up to go fast. AMPS tries to deliver messages at the fastest rate that an individual consumer can handle. AMPS has sophisticated machinery to try to find the fastest possible delivery rate for an individual consumer, and AMPS works hard1 to keep slower consumers...
amps messaging testing bookmark replay

Thumbnail: No Filesystem? No Problem! Keeping State in AMPS

  Mar 9, 2015   |      Dirk Myers

AMPS makes a great platform for distributing messages to worker processes. The combination of low latency delivery, the SOW last value cache, message replay, and powerful content filtering make it easy to build a scalable grid of workers. Update: This post describes an approach that was used with older versions...
amps messaging bookmark replay stateless

Thumbnail: Bookmark State Without a Filesystem: Ultimate Director's Cut

  Apr 6, 2023   |      Dirk Myers

AMPS bookmark subscriptions provide a way for applications to resume subscriptions in the event of a disconnection or failure of either the application or server. With a bookmark subscription, the application side manages the correct point to resume the subscription by setting a BookmarkStore on the client, and then discarding...
amps messaging bookmark replay stateless