sorentwo

defmodule Oban.Pro.Repo do
  use Ecto.Repo, otp_app: :oban_pro, adapter: Ecto.Adapters.Postgres
end

Application.ensure_all_started(:postgrex)
Oban.Pro.Repo.start_link()

defmodule BenchWorker do
  @moduledoc false

sorentwo

defmodule Oban.Pro.Clouds.Gigalixir do
  @moduledoc """
  Cloud scaler for Gigalixir.

  ## Usage

  ```elixir
  alias Oban.Pro.DynamicScaler
  alias Oban.Pro.Clouds.Gigalixir

sorentwo

defmodule Oban.Pro.Clouds.EC2ASG do
  @behaviour Oban.Pro.Cloud

  @impl Oban.Pro.Cloud
  def init(opts), do: Map.new(opts)

  @impl Oban.Pro.Cloud
  def scale(desired, conf) do
    params = %{
      "Action" => "SetDesiredCapacity",

sorentwo

defmodule Oban.Pro.Clouds.Heroku do
  @moduledoc false

  @behaviour Oban.Pro.Cloud

  @enforce_keys [:app, :auth_token, :dyno]
  defstruct @enforce_keys

  @impl Oban.Pro.Cloud
  def init(opts) do

sorentwo

defmodule Oban.Pro.Clouds.Fly do
  @moduledoc false

  @behaviour Oban.Pro.Cloud

  @enforce_keys [:app_id, :auth_token, :regions]
  defstruct @enforce_keys

  @url "https://api.fly.io/graphql"

sorentwo

version: 2
updates:
- package-ecosystem: mix
  directory: "/"
  schedule:
    interval: daily
    time: "11:00"
  open-pull-requests-limit: 10
  insecure-external-code-execution: allow
  registries:

sorentwo

Migrating background jobs to Elixir is easy with Oban because everything lives in your PostgreSQL database. Oban relies on a structured oban_jobs table as its job queue, and purposefully uses portable data structures (JSON) for serialization. That makes it enqueueing jobs into Oban simple for any language with a PostgreSQL adapter, no Oban client necessary.

As a demonstration, let's explore inserting Oban jobs from a Rails application.

To start, define a skeletal ActiveRecord model with a few conveniences for scheduling jobs:

sorentwo

defmodule QueueBreaker do
  @moduledoc """
  Automatic queue pausing/resuming based on accumulated errors.
  
  ## Example
  
  Pause after 1000 errors:
  
      QueueBreaker.attach("risky-queue", 1000)
  """

sorentwo

Single Page Oban Web

Application.put_env(:sample, Sample.Repo, database: "oban_dev")

Application.put_env(:phoenix, :json_library, Jason)

Application.put_env(:sample, Sample.Endpoint,
  http: [ip: {127, 0, 0, 1}, port: 5001],
  server: true,

sorentwo

Worker Hooks

Worker hooks are called after a job finishes executing. They can be defined as callback functions on the worker, or in a separate module for reuse across workers.

Hooks are called synchronously, from within the job's process with safety applied. Any exceptions or crashes are caught and logged, they won't cause the job to fail or the queue to crash.

Hooks do not modify the job or execution results. Think of them as a convenient alternative