Also for my last employer, I contributed to their private repo by building a web app that can allow People team to orchestrate IT on/off boarding tasks similar to a tool like (BetterCloud) but built in house. Source: almost 2 years ago

It's also called "SaaS management" or "software asset management" e.g. zylo.com bettercloud.com or blissfully.com. Source: over 2 years ago

Many mid-to-large sized organizations use BetterCloud to manage their Google Workspaces. If you use many SaaS products, you can probably manage most of them through their platform. Source: over 2 years ago

It is hard to imagine any big and complex Rails project without background jobs processing. There are many gems for this task: **Delayed Job, Sidekiq, Resque, SuckerPunch** and more. And Active Job has arrived here to rule them all. - Source: dev.to / 12 days ago

Rollbar is a great error-tracking service. It alerts us on exceptions and errors, provides analysis tools and dashboard, so we can see, reproduce, and fix bugs quickly when something went wrong. This service has a possibility to log not only uncaught exceptions but any messages. By default, the messages are reported synchronously, but you can enable asynchronous reporting using Sidekiq, girl_friday, or Resque.... - Source: dev.to / 14 days ago

You can use a background job queue like Resque to scrape and process data in the background, and a scheduler like resque-scheduler to schedule jobs to run your scraper periodically. Source: about 2 years ago

So how do we trigger such a long-running process from a Rails request? The first option that comes to mind is a background job run by some of the queuing back-ends such as Sidekiq, Resque or DelayedJob, possibly governed by ActiveJob. While this would surely work, the problem with all these solutions is that they usually have a limited number of workers available on the server and we didn’t want to potentially... - Source: dev.to / about 2 years ago

Background jobs are another limitation. Since only the Aha! Web service runs in a dynamic staging, the host environment's workers would process any Resque jobs that were sent to the shared Redis instance. If your branch hadn't updated any background-able methods, this would be no big deal. But if you were hoping to test changes to these methods, you would be out of luck. - Source: dev.to / about 2 years ago