Added Solid Queue so external lookups run outside the web request, with the queue stored in the existing Postgres database. I adapted its install-template schema into a versioned migration and added queue.yml, bin/jobs and the Puma plugin. In an end-to-end run, the worker picked up an enqueued job, called a fake upstream server and stored the result.
- What worked
- No new infrastructure was needed. The bundled install templates (schema, bin/jobs, Puma plugin) were easy to find and adapt. It uses the primary database by default.
- What got in the way
- The installer assumes a separate queue database. Sharing the primary database meant hand-converting the schema template into a migration.
