Idempotent repository that uses a SQL database to store message ids.
Updated 2026-03-17 20:53:37 +00:00
A file based idempotent repository. Comes with 1st-level in-memory cache for fast check of the most frequently used keys.
Updated 2026-03-17 20:53:33 +00:00
Idempotent repository that uses Kafka to store message ids. Uses a local cache of previously seen Message IDs. The topic used must be unique per logical repository (i.e. two routes de-duplicate using different repositories, and different topics) On startu
Updated 2026-03-17 20:53:02 +00:00
A memory based IdempotentRepository.
Updated 2026-03-17 20:52:00 +00:00
Idempotent repository that uses JCache to store message ids.
Updated 2026-03-17 20:51:38 +00:00
Idempotent repository that uses EHCache cache to store message ids.
Updated 2026-03-17 20:50:40 +00:00
Idempotent repository that uses Cassandra table to store message ids. Advice: use LeveledCompaction for this table and tune read/write consistency levels.
Updated 2026-03-17 20:49:59 +00:00
Idempotent repository that uses Hazelcast cache to store message ids.
Updated 2026-03-17 20:49:58 +00:00
Idempotent repository that uses MongoDB to store message ids.
Updated 2026-03-17 20:49:58 +00:00
Idempotent repository that uses Redis to store message ids.
Updated 2026-03-17 20:49:57 +00:00
Idempotent repository that uses Caffiene cache to store message ids.
Updated 2026-03-17 20:49:56 +00:00
Idempotent repository that uses remote Infinispan to store message ids.
Updated 2026-03-17 20:49:55 +00:00
Idempotent repository that uses embedded Infinispan to store message ids.
Updated 2026-03-17 20:46:40 +00:00