Run Services in the Background
Some time ago Marcin wrote about basic design patterns in Ruby on Rails. I’d like to go back to Service pattern in this post. I really like it, it’s a good idea to place application’s business logic there. At Naturaily we use it quite often.

Some time ago Marcin wrote about basic design patterns in Ruby on Rails. I’d like to go back to Service pattern in this post. I really like it, it's a good idea to place application’s business logic there. At Naturaily we use it quite often.
It happens that we need to run our service in the background. What's the easiest way to achieve this? Wrap our Service in a Job of course! Right... But we don't want to end up with dozens of very similar jobs. So... Here’s the solution. Let’s create universal Job for all the services.
Create the Job
Our job will be called ServiceInvocationJob. It's a good name for our universal job. To create a new Job we need to run one simple task:
tsx
And now we should edit newly created file. Right now it looks like this:
tsx
What do we need to run some service? Service's arguments, of course, and Service class itself! We can't pass class as argument, so we'll pass class' name. At the end our Job will be as simple as that:
tsx
Very nice? Don't you think?
Update BaseService class
We already run our services in the background jobs! Everywhere, where we want to run our service in background, we need to change classic invocation:
tsx
to this
tsx
But it doesn't look well. I think this one would be better:
tsx
Right?
So now we need to update our BaseService a bit! Nothing big. Just add a new static method called async_call. There's the updated file:
tsx
Summary
It is very easy, nothing fancy. However, there is a hidden message: you have to be lazy and remember that future-you is also lazy! You can create code that will solve your current problem (e. g. wrapper-job for your service), it's easy and fast, you don't need to think at all. But you should think a bit more and create code that will solve your problem and prevent the emergence of similar problems in the future(e. g. our ServiceInvocationJob). Future-you will be thankful.
Thank you! Bye!
Let’s Create a Great Website Together
We'll shape your web platform the way you win it!
More posts in this category

November 04, 2025 • 18 min read
READ MOREEssence of CDN: Benefits, Implementation, Meaning & Best Providers
CDN (Content Delivery Network) will speed up your website. Period. But how? And how do they work? Read on to learn more about the meaning and the benefits of CDN, providers, or implementation tactics. Let’s go!

October 28, 2025 • 8 min read
READ MOREHydrogen or Next.js for Shopify in 2026 - Which Should Your Business Choose (and When)?
Choosing between Shopify Hydrogen and Next.js is a strategic business decision. Your choice defines speed to market, long-term flexibility, cost predictability, and even your brand’s ability to innovate.

October 24, 2025 • 14 min read
READ MOREBest WordPress Alternatives in 2026: Which CMS Is Right for You?
WordPress continues to dominate the CMS landscape, powering around 43.3% of all websites and about 60.7% of those using a CMS. However, today’s web ecosystem has evolved significantly, offering a wide range of platforms tailored to different needs, from marketing and ecommerce to enterprise and developer-focused projects.
