Infinispan RESP in action: Resque use case

As you may know Infinispan 15 extended its RESP compatibility implementing most of the command related to the principal data types (set, list, hashes, sorted set…​).

In this post we want to present a demo case of integration between a real application (Resque) and Infinispan used as a Redis-compatible cache backend.
Aim of this is to show how it’s easy to switch between Redis and Infinispan making available to your application all the advanced features of our clustered cache server.

Resque is a job scheduler that creates jobs and send them to execution queues, it uses Redis as default backend and provides a testsuite and a demo application.
Try yourself how Infinispan can seamlessly replace the default backend: just clone this Resque fork and follow the Infinispan README to run both the test suite and the demo application.

Everything worked as a charm? Nice! Now check the diff with the original project, we only added code to turn on/off Infinispan instead of Redis. Nothing more than that! (*)

Hope you ejoyed this post!

Cheers,
The Infinispan Team

(*) What? You also noticed we changed the expected result for a test. Surely you can easily guess why…​ if not just ask us on Zulip!

Please, download and test the latest release.

The source code is hosted on GitHub. If you need to report a bug or request a new feature, look for a similar one on our JIRA issues tracker. If you don’t find any, create a new issue.

If you have questions, are experiencing a bug or want advice on using Infinispan, you can use GitHub discussions. We will do our best to answer you as soon as we can.

The Infinispan community uses Zulip for real-time communications. Join us using either a web-browser or a dedicated application on the Infinispan chat.