DEV Community

Cover image for Asynchronous task execution using Redis and Spring(Boot)
Sonu Kumar
Sonu Kumar

Posted on

Asynchronous task execution using Redis and Spring(Boot)

In this article, we are going to see how to use Spring boot 2.x and Redis to execute asynchronous tasks, with the final code that we will have after following the steps described here.

Spring/Spring Boot

Spring is the most popular framework available for the Java platform. Spring has one of the largest communities in open source. Besides that, Spring provides extensive and up-to-date documentation that covers the inner workings of the framework and sample projects on their blog, there’re 100K+ questions on StackOverflow.
Spring 3.0 was the first version that supported the annotation-based configuration, later in 2014 Spring boot 1.0 was released that completely changed how we look at the Spring framework ecosystems, it provides out of the box configuration and many more. Timeline


Redis is one of the most popular open-source NoSQL in-memory database. Redis supports different types of data structures e.g. Set, Hash table, List, simple key-value pair just name a few. The latency of Redis call is sub-milliseconds, support of a replica set, etc.

Why Asynchronous task execution

A typical API call consists of five things

  • Execute one or more database(RDBMS/NoSQL) queries
  • One or more operations on some cache systems (In-Memory, Distributed, etc )
  • Some computations (it could be some data crunching doing some math operations)
  • Calling some other service(s) (internal/external)
  • Schedule one or more tasks to be executed at a later time or immediately but in the background.

A task can be scheduled at a later time for many reasons for example invoice must be generated after 7 days of order creation or order shipment, similarly, email/notification(s) need not be sent immediately it can be delayed. Sometimes we need to execute tasks in asynchronous to reduce API response time, for example, delete 1K+ records at once if we delete all these records in the same API call then API response time would be increased for sure, to reduce API response time, we can run a task in the background that would delete those records.

Delayed queue

We can run schedule tasks using cron jobs, a cron job can be scheduled using different methods like UNIX style crontabs, Chronos, if we’re using Spring frameworks then it’s out of box Scheduled annotation ❤️. Most of these scheduling mechanisms suffer scaling problems, where we do scan database(s) to find the relevant rows/records. In many situations, this leads to a full table scan which performs very poorly. Imagine the case where the same database is used by a real-time application and this batch processing system. A delayed queue can be used in such cases where as soon as the timer reaches the scheduled time a job would be triggered. There’re many queuing systems/software available, but very few of them provide this feature, like SQS which provides a delay of 15 minutes, not an arbitrary delay like 7 hours or 7 days.


Rqueue is a broker built for the spring framework that stores data in Redis and provides a mechanism to execute a task at any arbitrary delay. Rqueue is backed by Redis since Redis has some advantages over the widely used queuing systems like Kafka, SQS. In most web applications backend, Redis is used to store either cache data orother purposese. In today's world, 8.4% of web applications are using the Redis database.

Alt Text

Generally, for a queue, we use either Kafka/SQS or some other systems these systems bring an additional overhead in different dimensions e.g money which can be reduced to zero using Rqueue and Redis.

Apart from the cost if we use Kafka then we need to do infrastructure setup, maintenance i.e. more ops, as most of the applications are already using Redis so we won’t have ops overhead, in fact, same Redis server/cluster can be used with Rqueue. Rqueue supports an arbitrary delay

Message Delivery
Rqueue guarantee at-least-once message delivery as long data is not wiped out from Redis. Read about it more at Introducing Rqueue

Tools we need:

  1. Any IDE 2. Gradle 3. Java 4. Redis We’re going to use Spring boot for simplicity, we’ll create a Gradle project from spring boot initializer at, for dependency we would need
    1. Spring Data Redis 2. Spring Web 3. Lombok and any others.

The directory/folder structure would look like below.

Alt Text

We’re going to use the Rqueue library to execute any tasks with any arbitrary delay. Rqueue is a Spring-based asynchronous task executor, that can execute tasks at any delay, it’s built upon the Spring messaging library and backed by Redis.
We’ll add the Rqueue spring boot starter dependency using com.github.sonus21:rqueue-spring-boot-starter:2.7.0-RELEASE

dependencies {
    implementation 'org.springframework.boot:spring-boot-starter-data-redis'
    implementation 'org.springframework.boot:spring-boot-starter-web'
    implementation 'com.github.sonus21:rqueue-spring-boot-starter:2.7.0-RELEASE'
    compileOnly 'org.projectlombok:lombok'
    annotationProcessor 'org.projectlombok:lombok'
    providedRuntime 'org.springframework.boot:spring-boot-starter-tomcat'
    testImplementation('org.springframework.boot:spring-boot-starter-test') {
        exclude group: 'org.junit.vintage', module: 'junit-vintage-engine'
Enter fullscreen mode Exit fullscreen mode

We need to enable Redis spring boot features, for testing purposes we will enable WEB MVC as well.
Update Application file as

public class AsynchronousTaskExecutorApplication {
   public static void main(String[] args) {, args);
Enter fullscreen mode Exit fullscreen mode

Adding tasks using Rqueue is very simple we need to just annotate a method with RqueueListener. RqueuListener annotation has multiple fields that can be set based on the use case, for example, set deadLetterQueue to push tasks to another queue otherwise task will be discarded on failure. We can also set how many times a task should be retried using the numRetries field.
Create a Java file name MessageListener and add some methods to execute tasks.

import com.github.sonus21.rqueue.annotation.RqueueListener;
import lombok.extern.slf4j.Slf4j;
import org.springframework.stereotype.Component;

public class MessageListener {

  @RqueueListener(value = "${}")
  public void sendEmail(Email email) {"Email {}", email);

  @RqueueListener(value = "${}")
  public void generateInvoice(Invoice invoice) {"Invoice {}", invoice);
Enter fullscreen mode Exit fullscreen mode

We would need Email and Invoice classes to store email and invoice data respectively. For simplicity, classes would only have a handful number of fields.

import lombok.AllArgsConstructor;
import lombok.Data;
import lombok.NoArgsConstructor;

public class Invoice {
  private String id;
  private String type;
Enter fullscreen mode Exit fullscreen mode

import lombok.AllArgsConstructor;
import lombok.Data;
import lombok.NoArgsConstructor;

public class Email {
  private String email;
  private String subject;
  private String content;
Enter fullscreen mode Exit fullscreen mode

Task submissions

A task can be submitted using the RqueueMessageEnqueuer bean. This has multiple methods to enqueue tasks depending on the use case, like retry use, retry count, and delay for delayed tasks.

We need to AutoWire RqueueMessageEnqueuer or use constructor to inject this bean.

Create a Controller for testing purpose:
We’re going to schedule invoice generation that would be done in the next 30 seconds, for this we’ll submit a task with 30000 (milliseconds) delay on invoice queue. Also, we’ll try to send an email that will be done in the background. For this purpose, we’ll add two GET methods sendEmail and generateInvoice, we can use POST as well.

@RequiredArgsConstructor(onConstructor = @__(@Autowired))
public class Controller {
  private @NonNull RqueueMessageEnqueuer rqueueMessageEnqueuer;

  private String emailQueueName;

  private String invoiceQueueName;

  private Long invoiceDelay;

  public String sendEmail(
      @RequestParam String email, @RequestParam String subject, @RequestParam String content) {"Sending email");
    rqueueMessageEnqueuer.enqueue(emailQueueName, new Email(email, subject, content));
    return "Please check your inbox!";

  public String generateInvoice(@RequestParam String id, @RequestParam String type) {"Generate invoice");
    rqueueMessageEnqueuer.enqueueIn(invoiceQueueName, new Invoice(id, type), invoiceDelay);
    return "Invoice would be generated in " + invoiceDelay + " milliseconds";
Enter fullscreen mode Exit fullscreen mode

Add the following in the file

30 seconds delay for invoice


It’s time to fire up the spring boot application, once the application starts successfully, browse


In the log, we can see tasks are being executed in the background

Alt Text

Invoice scheduling after 30 seconds

Alt Text

In conclusion, we can schedule tasks using Rqueue without much of the boiler code. We need to consider a few things while configuring the Rqueue library and using them. One of the important is whether a task is a delayed task or not; by default, it’s assumed tasks need to be executed as soon as possible.

Complete code can be found at my Github account

Rqueue library code:

If you found this post helpful please share across and give a thumbs up.

Top comments (0)