Full Stack JavaScript Strategies

Chapter 6. Background Jobs

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 6th chapter of the final book.

If you have comments about how we might improve the content and/or examples in this book, or if you notice missing material within this chapter, please reach out to the author at [e-mail].

Once you have some third-party integrations, it’s likely that you’ll end up needing automated ways to keep the company’s data in sync with the third party’s data and to trigger other events like sending emails. That’s where background jobs and cron jobs come in.

A background job executes code or actions that need to run outside the flow of an API in a systematic way. This will include tasks like sending emails or doing complex calculations after a user has made an update. Background jobs are going to work alongside your server-side application code and are typically triggered directly from an endpoint call. These jobs are usually defined at the service level because they typically have business logic around them.

A cron job is a task that is executed on a schedule. It will run at some time interval you set based on the business needs. Syncing data from or to a third-party service on a schedule is a prime example of using a cron job. Cron jobs can be in your ...