1
0
Fork 0
mirror of https://github.com/mperham/sidekiq.git synced 2022-11-09 13:52:34 -05:00
This commit is contained in:
Mike Perham 2022-06-05 07:50:03 -07:00
parent 55ced28181
commit f17c30cfff
2 changed files with 4 additions and 4 deletions

View file

@ -2,11 +2,11 @@
[Sidekiq Changes](https://github.com/mperham/sidekiq/blob/main/Changes.md) | [Sidekiq Pro Changes](https://github.com/mperham/sidekiq/blob/main/Pro-Changes.md) | [Sidekiq Enterprise Changes](https://github.com/mperham/sidekiq/blob/main/Ent-Changes.md)
HEAD
6.5.0
---------
- Substantial refactoring of Sidekiq server internals, as part of a larger effort to
reduce Sidekiq's internal usage of global methods and data, see [docs/component.md].
reduce Sidekiq's internal usage of global methods and data, see [[docs/component.md]] and [[docs/global_to_local.md]].
- Add **beta** support for the `redis-client` gem**. This will become the default Redis driver in Sidekiq 7.0. [#5298]
Read more: https://github.com/mperham/sidekiq/wiki/Using-redis-client
- Add **beta** support for DB transaction-aware client [#5291]

View file

@ -1,4 +1,4 @@
# Reducing Global API usage in Sidekiq
# Reducing Global API usage in Sidekiq 7.0
In Sidekiq 6.x, we rely heavily on top-level APIs and options within the Sidekiq module itself. APIs like `Sidekiq.options` are used everywhere to pull dynamic configuration.
This makes Sidekiq incompatible with Ractors or embedding within other processes.
@ -21,7 +21,7 @@ Sidekiq.configure_server do |config|
end
```
Let me be clear: `Sidekiq.configure_{client,server}` will remain supported for the
To be clear: `Sidekiq.configure_{client,server}` will remain supported for the
foreseeable future. How Sidekiq works by default will remain very, very similar but these
small tweaks will allow a new mode of operation for Sidekiq and unlock a few, new usecases...