Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should we continue to use Sidekiq as our preferred queuing backend? #1210

Open
Tracked by #1213
stevepolitodesign opened this issue May 30, 2024 · 2 comments
Open
Tracked by #1213
Labels
Discussion Needs feedback

Comments

@stevepolitodesign
Copy link
Contributor

The upcoming release of Rails 8 is slated to use Solid Queue as the default queuing backend.

We currently default to Sidekiq.

Should we continue to use Sidekiq as our preferred queuing backend, or, should we use the new Rails default?

@stevepolitodesign stevepolitodesign added Enhancement Features we're considering adding Discussion Needs feedback and removed Enhancement Features we're considering adding labels Jun 6, 2024
@stevepolitodesign
Copy link
Contributor Author

If we're not ready to use Solid Queue in favor of Sidekiq, we should skip it with --skip-solid when running rails new

@stevepolitodesign
Copy link
Contributor Author

Another thing to consider is hosting. If we don't call --skip-solid, then we end up with 4 databases:

production:
  primary: &primary_production
    <<: *default
    database: rails_8_production
    username: rails_8
    password: <%= ENV["RAILS_8_DATABASE_PASSWORD"] %>
  cache:
    <<: *primary_production
    database: rails_8_production_cache
    migrations_paths: db/cache_migrate
  queue:
    <<: *primary_production
    database: rails_8_production_queue
    migrations_paths: db/queue_migrate
  cable:
    <<: *primary_production
    database: rails_8_production_cable
    migrations_paths: db/cable_migrate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Discussion Needs feedback
Projects
None yet
Development

No branches or pull requests

1 participant