In this article, learn about Tickler, a new expiring item service for a Microservice environment, and when you may need to use it.

First, let’s define the need for Tickler:

I am, as a Tickler client application, running in distributed microservice environment and I need an expiring distributed data structure in which all of the items in this structure may have different time-to-live values.

These JSON-based expiring items can be called reminders (tickles), which are composed of a callback URL of the client or callback Kafka topic which is consumed by the client, JSON payload for the callback, and a TTL value in seconds.

The main components of a Tickler client and Tickler main application nodes are stated on the image below:

#redis #microservice architecture #microservice components #microservice