Unlocking the Magic of perform_async in Ruby on Rails

January 9, 2025

Have you ever wished you could delegate tasks to an invisible assistant while you focus on what’s important? Well, in the world of Ruby on Rails, perform_async from the Sidekiq gem is that magical assistant! It helps you move tasks to the background, letting your application handle more important things—like keeping your users happy.

But first, let’s set the stage.

---

What Is perform_async?

perform_async is a method provided by Sidekiq , a popular library for background job processing in Ruby. This method allows you to enqueue tasks that might take time to complete (e.g., sending emails, processing images, or crunching numbers). By moving these tasks out of the main request-response cycle, your application can respond faster and stay snappy.

Here’s the recipe:

1. Include the Worker Module : Start by creating a worker class and including Sidekiq::Worker.
2. Define the Job Logic : Add a perform method with the task logic.
3. Call perform_async: Use this method to enqueue the job with any required arguments.

A Practical Example

Let’s say we want to send a welcome email to a new user. Here’s how it looks:

# app/workers/welcome_email_worker.rb
class WelcomeEmailWorker
  include Sidekiq::Worker

  def perform(user_id)
    user = User.find(user_id)
    UserMailer.welcome_email(user).deliver_now
  end
end

# Somewhere in your app…
WelcomeEmailWorker.perform_async(new_user.id)

When perform_async is called, the job is added to a Redis queue. A Sidekiq worker process will pick it up and run it in the background. Your app’s main thread can breathe a sigh of relief, knowing the task is being handled elsewhere.

Why Is This So Powerful?

Here are a few reasons why perform_async deserves the spotlight:

• Speed : Your app can respond to users faster by offloading long-running tasks.
• Scalability : Sidekiq processes jobs concurrently, making it efficient for handling thousands of tasks.
• Simplicity : The API is intuitive, so even newcomers can jump right in.

A Little Humor: Background Jobs in Real Life

Imagine you’re hosting a dinner party. You could:

1. Cook the entire meal, serve drinks, clean dishes, and entertain guests yourself…while they wonder why you’re sweating.
2. Delegate cooking to the chef (Sidekiq), bartending to a mixologist (Redis), and cleaning to the dishwasher (background workers).

Option 2 sounds better, doesn’t it? That’s the beauty of perform_async. It’s like telling your app, “Hey, take care of this when you have a moment,” and then going back to what truly matters.

---

Pro Tips for Using perform_async

• Retry Logic : Sidekiq has built-in retry mechanisms, so failed jobs can be retried automatically.
• Job Prioritization : Use different queues to prioritize critical jobs.
• Monitoring : Use the Sidekiq Web UI to track job status and troubleshoot issues.

---

Wrapping It Up

perform_async is your app’s secret weapon for staying agile and efficient. By offloading tasks to the background, you’re giving your app room to grow and your users a seamless experience. So, next time you find your app bogged down with heavy lifting, remember: Sidekiq’s got your back.

And who knows, maybe we’ll soon have perform_async for real life. Need groceries? “.perform_async.” Forgot to water the plants? “.perform_async.” Until then, let’s keep using it to make our Rails apps shine!

Do you need more hands for your Ruby on Rails project?

Fill out our form! >>

Do you need more hands for your Ruby on Rails project?