super_spreader 0.1.0.beta2 → 0.1.0

data/Gemfile.lock

@@ -1,196 +0,0 @@
-PATH
-  remote: .
-  specs:
-    super_spreader (0.1.0.beta2)
-      activejob (>= 6.1, < 8.0)
-      activemodel (>= 6.1, < 8.0)
-      activerecord (>= 6.1, < 8.0)
-      activesupport (>= 6.1, < 8.0)
-      redis (>= 4.8, < 6.0)
-
-GEM
-  remote: https://rubygems.org/
-  specs:
-    actionpack (6.1.4.7)
-      actionview (= 6.1.4.7)
-      activesupport (= 6.1.4.7)
-      rack (~> 2.0, >= 2.0.9)
-      rack-test (>= 0.6.3)
-      rails-dom-testing (~> 2.0)
-      rails-html-sanitizer (~> 1.0, >= 1.2.0)
-    actionview (6.1.4.7)
-      activesupport (= 6.1.4.7)
-      builder (~> 3.1)
-      erubi (~> 1.4)
-      rails-dom-testing (~> 2.0)
-      rails-html-sanitizer (~> 1.1, >= 1.2.0)
-    activejob (6.1.4.7)
-      activesupport (= 6.1.4.7)
-      globalid (>= 0.3.6)
-    activemodel (6.1.4.7)
-      activesupport (= 6.1.4.7)
-    activerecord (6.1.4.7)
-      activemodel (= 6.1.4.7)
-      activesupport (= 6.1.4.7)
-    activesupport (6.1.4.7)
-      concurrent-ruby (~> 1.0, >= 1.0.2)
-      i18n (>= 1.6, < 2)
-      minitest (>= 5.1)
-      tzinfo (~> 2.0)
-      zeitwerk (~> 2.3)
-    ast (2.4.2)
-    builder (3.2.4)
-    coderay (1.1.3)
-    concurrent-ruby (1.1.10)
-    connection_pool (2.4.1)
-    crass (1.0.6)
-    diff-lcs (1.5.0)
-    erubi (1.12.0)
-    factory_bot (4.11.1)
-      activesupport (>= 3.0.0)
-    ffi (1.15.5)
-    formatador (1.1.0)
-    globalid (1.1.0)
-      activesupport (>= 5.0)
-    guard (2.18.0)
-      formatador (>= 0.2.4)
-      listen (>= 2.7, < 4.0)
-      lumberjack (>= 1.0.12, < 2.0)
-      nenv (~> 0.1)
-      notiffany (~> 0.0)
-      pry (>= 0.13.0)
-      shellany (~> 0.0)
-      thor (>= 0.18.1)
-    guard-compat (1.2.1)
-    guard-rspec (4.7.3)
-      guard (~> 2.1)
-      guard-compat (~> 1.1)
-      rspec (>= 2.99.0, < 4.0)
-    i18n (1.12.0)
-      concurrent-ruby (~> 1.0)
-    json (2.6.3)
-    language_server-protocol (3.17.0.2)
-    listen (3.7.1)
-      rb-fsevent (~> 0.10, >= 0.10.3)
-      rb-inotify (~> 0.9, >= 0.9.10)
-    loofah (2.19.1)
-      crass (~> 1.0.2)
-      nokogiri (>= 1.5.9)
-    lumberjack (1.2.8)
-    method_source (1.0.0)
-    mini_portile2 (2.8.4)
-    minitest (5.17.0)
-    nenv (0.3.0)
-    nokogiri (1.15.4)
-      mini_portile2 (~> 2.8.2)
-      racc (~> 1.4)
-    notiffany (0.1.3)
-      nenv (~> 0.1)
-      shellany (~> 0.0)
-    parallel (1.22.1)
-    parser (3.2.0.0)
-      ast (~> 2.4.1)
-    pry (0.14.1)
-      coderay (~> 1.1)
-      method_source (~> 1.0)
-    racc (1.7.1)
-    rack (2.2.8)
-    rack-test (2.0.2)
-      rack (>= 1.3)
-    rails-dom-testing (2.0.3)
-      activesupport (>= 4.2.0)
-      nokogiri (>= 1.6)
-    rails-html-sanitizer (1.4.4)
-      loofah (~> 2.19, >= 2.19.1)
-    railties (6.1.4.7)
-      actionpack (= 6.1.4.7)
-      activesupport (= 6.1.4.7)
-      method_source
-      rake (>= 0.13)
-      thor (~> 1.0)
-    rainbow (3.1.1)
-    rake (10.5.0)
-    rb-fsevent (0.11.2)
-    rb-inotify (0.10.1)
-      ffi (~> 1.0)
-    redis (5.0.6)
-      redis-client (>= 0.9.0)
-    redis-client (0.14.1)
-      connection_pool
-    regexp_parser (2.6.1)
-    rexml (3.2.5)
-    rspec (3.12.0)
-      rspec-core (~> 3.12.0)
-      rspec-expectations (~> 3.12.0)
-      rspec-mocks (~> 3.12.0)
-    rspec-core (3.12.0)
-      rspec-support (~> 3.12.0)
-    rspec-expectations (3.12.1)
-      diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.12.0)
-    rspec-mocks (3.12.1)
-      diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.12.0)
-    rspec-rails (4.1.2)
-      actionpack (>= 4.2)
-      activesupport (>= 4.2)
-      railties (>= 4.2)
-      rspec-core (~> 3.10)
-      rspec-expectations (~> 3.10)
-      rspec-mocks (~> 3.10)
-      rspec-support (~> 3.10)
-    rspec-support (3.12.0)
-    rspec_junit_formatter (0.6.0)
-      rspec-core (>= 2, < 4, != 2.12.0)
-    rubocop (1.42.0)
-      json (~> 2.3)
-      parallel (~> 1.10)
-      parser (>= 3.1.2.1)
-      rainbow (>= 2.2.2, < 4.0)
-      regexp_parser (>= 1.8, < 3.0)
-      rexml (>= 3.2.5, < 4.0)
-      rubocop-ast (>= 1.24.1, < 2.0)
-      ruby-progressbar (~> 1.7)
-      unicode-display_width (>= 1.4.0, < 3.0)
-    rubocop-ast (1.24.1)
-      parser (>= 3.1.1.0)
-    rubocop-performance (1.15.2)
-      rubocop (>= 1.7.0, < 2.0)
-      rubocop-ast (>= 0.4.0)
-    ruby-progressbar (1.11.0)
-    shellany (0.0.1)
-    sqlite3 (1.6.0)
-      mini_portile2 (~> 2.8.0)
-    standard (1.21.1)
-      language_server-protocol (~> 3.17.0.2)
-      rubocop (= 1.42.0)
-      rubocop-performance (= 1.15.2)
-    thor (1.2.1)
-    tzinfo (2.0.5)
-      concurrent-ruby (~> 1.0)
-    unicode-display_width (2.4.2)
-    webrick (1.7.0)
-    yard (0.9.28)
-      webrick (~> 1.7.0)
-    zeitwerk (2.6.6)
-
-PLATFORMS
-  ruby
-
-DEPENDENCIES
-  bundler
-  factory_bot
-  guard
-  guard-rspec
-  pry
-  rake
-  rspec
-  rspec-rails
-  rspec_junit_formatter
-  sqlite3
-  standard
-  super_spreader!
-  yard
-
-BUNDLED WITH
-   2.1.4

data/Guardfile

@@ -1,18 +0,0 @@
-# frozen_string_literal: true
-
-guard :rspec, cmd: "bundle exec rspec" do
-  require "guard/rspec/dsl"
-  dsl = Guard::RSpec::Dsl.new(self)
-
-  # RSpec files
-  rspec = dsl.rspec
-  watch(rspec.spec_helper) { rspec.spec_dir }
-  watch(rspec.spec_support) { rspec.spec_dir }
-  watch(rspec.spec_files)
-
-  # Ruby files
-  ruby = dsl.ruby
-  dsl.watch_spec_files_for(ruby.lib_files)
-
-  watch(%r{lib/super_spreader/(.+).(rb|rake)}) { |m| "spec/#{m[1]}_spec.rb" }
-end

data/LICENSE.txt

@@ -1,13 +0,0 @@
-Copyright 2023 Doximity, Inc.
-
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-    http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.

data/README.md

@@ -1,240 +0,0 @@
-# SuperSpreader
-
-SuperSpreader is a library for massive, memory- and compute-efficient backfills of ActiveRecord models using ActiveJob.
-
-This tool is built to backfill many millions of records in a resource-efficient way.  When paired with a properly written job, it can drastically reduce the wall time of a backfill through parallelization.  Jobs are enqueued in small batches so that the ActiveJob backend is not overwhelmed.  These jobs can also be stopped at a moment's notice, if needed.
-
-## Example use cases
-
-- Re-encrypt data
-- Make API calls to fill in missing data
-- Restructuring complex data
-
-## Warnings
-
-> [!WARNING]
->
-> **Please be aware:** SuperSpreader is still fairly early in development.  While it can be used effectively by experienced hands, we are aware that it could have a better developer experience (DevX).  It was written to solve a specific problem (see "History").  We are working to generalize the tool as the need arises.  Pull requests are welcome!
-
-Please also see "Roadmap" for other known limitations that may be relevant to you.
-
-## History
-
-SuperSpreader was originally written to re-encrypt the Dialer database, a key component of Doximity's telehealth offerings.  Without SuperSpreader, it would have taken **several months** to handle many millions of records using a Key Management Service (KMS) that adds an overhead of 11 ms per record.  Using SuperSpreader took the time to backfill down to a couple of weeks.  This massive backfill happened safely during very high Dialer usage during the winter of 2020.  Of course, the name came from the coronavirus pandemic, which had a number of super-spreader events in the news around the same time.  Rather than spreading disease, the SuperSpreader gem spreads out telehealth background jobs to support the healthcare professionals that fight disease.
-
-Since that time, our team has started to use SuperSpreader in many other situations.  Our hope is that other teams, internal and external, can use it if they have similar problems to solve.
-
-## When should I use it?
-
-SuperSpreader was built for backfills.  If you need to touch every record and you have _a lot_ of records, it may be a good fit.
-
-That said, it's **not** common to need a tool like SuperSpreader.  Many backfills are better handled through SQL or Rake tasks.  SuperSpreader should only be used when the additional complexity is warranted.  Before using a shiny tool, **please stop and consider the tradeoffs**.
-
-For some use cases, a pure-SQL migration or Rake task may be a better fit.  It may also make sense to use **both** background jobs and foreground task (Rails migration or Rake task).  (Consider the database size and number of instances between production and staging.)  For that, you might consider [SuperSpreader::BatchHelper](https://github.com/doximity/super_spreader/blob/master/lib/super_spreader/batch_helper.rb).
-
-The primary criterion to consider is whether the backfill in question is _long-running_.  If you estimate it would take at least a couple of days to complete, it makes sense to consider SuperSpreader.  Another good reason to consider this tool is _code reuse_.  If you already have Ruby-land code that would be difficult or impossible to replicate in SQL, it makes sense to use SuperSpreader, assuming the equivalent Rake task would be impractical.
-
-## How does it work?
-
-SuperSpreader enqueues a configurable number of background jobs on a set schedule.  These background jobs are executed in small batches such that only a small number of jobs are enqueued at any given time.  The jobs start at the most recent record and work back to the first record, based on the auto-incrementing primary key.
-
-The configuration is able to be tuned for the needs of an individual problem.  If the backfill would require months of compute time, it can be run in parallel so that it takes much less time.  The resource utilization can be spread out so that shared resources, such as a database, are not overwhelmed with requests.  Finally, there is also support for running more jobs during off-peak usage based on a schedule.
-
-Backfills are implemented using ActiveJob classes.  SuperSpreader orchestrates running those jobs.  Each set of jobs is enqueued by a scheduler using the supplied configuration.
-
-As an example, assume that there's a table with 100,000,000 rows which need Ruby-land logic to be applied using `ExampleBackfillJob`.  The rate (e.g., how many jobs per second) is configurable.  Once configured, SuperSpreader would enqueue job in batches like:
-
-    ExampleBackfillJob run_at: "2020-11-16T22:51:59Z", begin_id: 99_999_901, end_id: 100_000_000
-    ExampleBackfillJob run_at: "2020-11-16T22:51:59Z", begin_id: 99_999_801, end_id:  99_999_900
-    ExampleBackfillJob run_at: "2020-11-16T22:51:59Z", begin_id: 99_999_701, end_id:  99_999_800
-    ExampleBackfillJob run_at: "2020-11-16T22:52:00Z", begin_id: 99_999_601, end_id:  99_999_700
-    ExampleBackfillJob run_at: "2020-11-16T22:52:00Z", begin_id: 99_999_501, end_id:  99_999_600
-    ExampleBackfillJob run_at: "2020-11-16T22:52:00Z", begin_id: 99_999_401, end_id:  99_999_500
-
-Notice that there are 3 jobs per second, 2 seconds of work were enqueued, and the batch size is 100.  Again, this is just an example for illustration, and the configuration can be modified to suit the needs of the problem.
-
-After running out of work, SuperSpreader will enqueue more work:
-
-    SuperScheduler::SchedulerJob run_at: "2020-11-16T22:52:01Z"
-
-And the work continues:
-
-    ExampleBackfillJob run_at: "2020-11-16T22:52:01Z", begin_id: 99_999_401, end_id:  99_999_500
-    ExampleBackfillJob run_at: "2020-11-16T22:52:01Z", begin_id: 99_999_301, end_id:  99_999_400
-    ExampleBackfillJob run_at: "2020-11-16T22:52:01Z", begin_id: 99_999_201, end_id:  99_999_300
-    ExampleBackfillJob run_at: "2020-11-16T22:52:02Z", begin_id: 99_999_101, end_id:  99_999_200
-    ExampleBackfillJob run_at: "2020-11-16T22:52:02Z", begin_id: 99_999_001, end_id:  99_999_100
-    ExampleBackfillJob run_at: "2020-11-16T22:52:02Z", begin_id: 99_998_901, end_id:  99_999_000
-
-This process continues until there is no more work to be done.  For more detail, please see [Spreader](https://github.com/doximity/super_spreader/blob/master/lib/super_spreader/spreader.rb) and [its spec](https://github.com/doximity/super_spreader/blob/master/spec/spreader_spec.rb).
-
-Additionally, the configuration can be tuned while SuperSpreader is running.  The configuration is read each time `SchedulerJob` runs.  As it stands, each run of SuperSpreader is hand-tuned.  It is highly recommended that SuperSpreader resource utilization is monitored during runs.  That said, it is designed to run autonomously once a good configuration is found.
-
-Example tuning:
-
-- Does the process need to go faster?  Increase the number of jobs per second.
-- Are batches taking too long to complete?  Decrease the batch size.
-- Is `SchedulerJob` taking a long time to complete?  Decrease the duration so that less work is enqueued in each cycle.
-
-Finally, SuperSpreader can be stopped instantly and resumed at a later time, if a need ever arises.
-
-## How do I use it?
-
-To repeat an earlier disclaimer:
-
-> **Please be aware:** SuperSpreader is still fairly early in development.  While it can be used  by experienced hands, we are aware that it could have a better developer experience (DevX).  It was written to solve a specific problem (see "History").  We are working to generalize the tool as the need arises.  Pull requests are welcome!
-
-If you haven't yet, please read the "How does it work?" section.  This basic workflow is tested in `spec/integration/backfill_spec.rb`.
-
-First, write a backfill job.  Please see [this example for details](https://github.com/doximity/super_spreader/blob/master/spec/support/example_backfill_job.rb).
-
-Next, configure `SuperSpreader` from the console by saving `SchedulerConfig` to Redis.  For documentation on each attribute, please see [SchedulerConfig](https://github.com/doximity/super_spreader/blob/master/lib/super_spreader/scheduler_config.rb).  It is recommended that you start slow, with small batches, short durations, and low per-second rates.
-
-**Important:** SuperSpreader currently only supports a _single_ configuration, though removing that limitation is our Roadmap (please see below).
-
-```ruby
-# NOTE: This is an example.  You should take your situation into account when
-# setting these values.
-config = SuperSpreader::SchedulerConfig.new
-
-config.batch_size = 10
-config.duration = 10
-config.job_class_name = "ExampleBackfillJob"
-
-config.per_second_on_peak = 3.0
-config.per_second_off_peak = 3.0
-
-config.on_peak_timezone = "America/Los_Angeles"
-config.on_peak_wday_begin = 1
-config.on_peak_wday_end = 5
-config.on_peak_hour_begin = 5
-config.on_peak_hour_end = 17
-
-config.save
-```
-
-Now the `SchedulerJob` can be started.  It will run until it is stopped or runs out of work.
-
-```ruby
-SuperSpreader::SchedulerJob.perform_now
-```
-
-At this point, you should monitor your database and worker instances using the tooling you have available.  You should make adjustments based on the metrics you have available.
-
-Based on those metrics, slowly step up `per_second_on_peak` and `batch_size` while continuing to monitor:
-
-```ruby
-config.batch_size = 20
-config.save
-```
-
-```ruby
-config.per_second_on_peak = 4.0
-config.save
-```
-
-Continue to step up the rates, until you arrive at a rate that is acceptable for your situation.
-For our re-encryption project as an example, our jobs ran at this rate:
-
-```ruby
-# NOTE: This is an example.  You should take your situation into account when
-# setting these values.
-config = SuperSpreader::SchedulerConfig.new
-
-config.batch_size = 70
-config.duration = 180
-config.job_class_name = "ReencryptJob"
-
-config.per_second_on_peak = 3.0
-config.per_second_off_peak = 7.5
-
-config.on_peak_timezone = "America/Los_Angeles"
-config.on_peak_wday_begin = 1
-config.on_peak_wday_end = 5
-config.on_peak_hour_begin = 5
-config.on_peak_hour_end = 17
-
-config.save
-```
-
-### Disaster recovery
-
-If at any point you need to stop the background jobs, stop all scheduling using:
-
-```ruby
-SuperSpreader::SchedulerJob.stop!
-```
-
-Optionally, if it is acceptable to have a partially-processed cycle, you can stop the backfill jobs as well:
-
-```ruby
-ExampleBackfillJob.stop!
-```
-
-(Recovering from a partially-processed cycle requires manually setting the correct `initial_id` in `SpreadTracker`.)
-
-The jobs will still be present in the job runner, but will all execute instantly because of the early return as demonstrated in [the example job](https://github.com/doximity/super_spreader/blob/master/spec/support/example_backfill_job.rb).  After the last scheduler job, the process will be paused.
-
-### Restarting
-
-If you stop the jobs but you wish to restart them later, use the `go!` method and *then* call `SuperSpreader::SchedulerJob.perform_now`.  Otherwise, the jobs will not do any work.
-
-```ruby
-ExampleBackfillJob.go!
-SuperSpreader::SchedulerJob.go!
-SuperSpreader::SchedulerJob.perform_now
-```
-
-## Installation
-
-If you've gotten this far and think SuperSpreader is a good fit for your problem, these are the instructions for installing it.
-
-Add this line to your application's Gemfile:
-
-```ruby
-gem 'super_spreader'
-```
-
-And then execute:
-
-    $ bundle
-
-Or install it yourself as:
-
-    $ gem install super_spreader
-
-SuperSpreader requires an ActiveRecord-compatible database, an ActiveJob-compatible job runner, and Redis for bookkeeping.
-
-For Rails, please set up SuperSpreader using an initializer:
-
-```ruby
-# config/initializers/super_spreader.rb
-
-SuperSpreader.logger = Rails.logger
-SuperSpreader.redis = Redis.new(url: ENV["REDIS_URL"])
-```
-
-## Roadmap
-
-Please see [the Milestones on GitHub](https://github.com/doximity/super_spreader/milestones?direction=asc&sort=title&state=open).
-
-## Development
-
-You'll need [Redis](https://redis.io/docs/getting-started/) and [Ruby](https://www.ruby-lang.org/en/downloads/) installed.  Please ensure both are set up before continuing.
-
-After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
-
-To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
-
-## Contributing
-
-1. See [CONTRIBUTING.md](./CONTRIBUTING.md)
-2. Fork it ( https://github.com/doximity/super_spreader/fork )
-3. Create your feature branch (`git checkout -b my-new-feature`)
-4. Commit your changes (`git commit -am 'Add some feature'`)
-5. Push to the branch (`git push origin my-new-feature`)
-6. Create a new Pull Request
-
-## License
-
-`super_spreader` is licensed under an Apache 2 license. Contributors are required to sign a contributor license agreement. See LICENSE.txt and CONTRIBUTING.md for more information.

data/Rakefile

@@ -1,35 +0,0 @@
-require "bundler/gem_tasks"
-require "rspec/core/rake_task"
-require "yard"
-
-RSpec::Core::RakeTask.new(:spec)
-YARD::Rake::YardocTask.new(:doc)
-
-task default: :spec
-
-desc "Run a REPL with access to this library"
-task :console do
-  sh("irb -I lib -r super_spreader")
-end
-
-namespace :check do
-  desc "Run all checks"
-  task all: %i[redis]
-
-  desc "Confirm Redis is accessible"
-  task :redis do
-    require "redis"
-
-    inaccessible_error_message = "Redis: inaccessible (please confirm that a Redis server is installed and running, e.g. redis-server)"
-
-    redis = Redis.new(url: ENV["REDIS_URL"])
-
-    if redis.ping == "PONG"
-      puts "Redis: OK"
-    else
-      raise inaccessible_error_message
-    end
-  rescue Redis::CannotConnectError
-    raise inaccessible_error_message
-  end
-end

data/bin/console

@@ -1,14 +0,0 @@
-#!/usr/bin/env ruby
-
-require "bundler/setup"
-require "super_spreader"
-
-# You can add fixtures and/or initialization code here to make experimenting
-# with your gem easier. You can also use a different console, if you like.
-
-# (If you use this, don't forget to add pry to your Gemfile!)
-# require "pry"
-# Pry.start
-
-require "irb"
-IRB.start(__FILE__)

data/bin/setup

@@ -1,7 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-IFS=$'\n\t'
-set -vx
-
-bundle install
-rake check:all

data/lib/super_spreader/batch_helper.rb

@@ -1,40 +0,0 @@
-# frozen_string_literal: true
-
-require "active_record"
-
-module SuperSpreader
-  # Methods in this module are suitable for use in Rails migrations.  It is
-  # expected that their interface will remain stable.  If breaking changes are
-  # introduced, a new module will be introduced so existing migrations will not
-  # be affected.
-  module BatchHelper
-    # Execute SQL in small batches for an entire table.
-    #
-    # It is assumed that the table has a primary key named +id+.
-    #
-    # Recommendation for migrations: Use this in combination with +disable_ddl_transaction!+.
-    # See also: https://github.com/ankane/strong_migrations#backfilling-data
-    #
-    # @param table_name [String] the name of the table
-    # @param step_size [Integer] how many records to process in each batch
-    # @yield [minimum_id, maximum_id] block that returns SQL to migrate records between minimum_id and maximum_id
-    def batch_execute(table_name:, step_size:)
-      result = execute(<<~SQL).to_a.flatten
-        SELECT MIN(id) AS min_id, MAX(id) AS max_id FROM #{quote_table_name(table_name)}
-      SQL
-      min_id = result[0]["min_id"]
-      max_id = result[0]["max_id"]
-      return unless min_id && max_id
-
-      lower_id = min_id
-      loop do
-        sql = yield(lower_id, lower_id + step_size)
-
-        execute(sql)
-
-        lower_id += step_size
-        break if lower_id > max_id
-      end
-    end
-  end
-end

data/lib/super_spreader/peak_schedule.rb

@@ -1,22 +0,0 @@
-# frozen_string_literal: true
-
-require "active_support/core_ext/time"
-
-module SuperSpreader
-  class PeakSchedule
-    def initialize(on_peak_wday_range:, on_peak_hour_range:, timezone:)
-      @on_peak_wday_range = on_peak_wday_range
-      @on_peak_hour_range = on_peak_hour_range
-      @timezone = timezone
-    end
-
-    def on_peak?(time = Time.current)
-      time_in_zone = time.in_time_zone(@timezone)
-
-      is_on_peak_day = @on_peak_wday_range.cover?(time_in_zone.wday)
-      is_on_peak_hour = @on_peak_hour_range.cover?(time_in_zone.hour)
-
-      is_on_peak_day && is_on_peak_hour
-    end
-  end
-end

data/lib/super_spreader/redis_model.rb

@@ -1,51 +0,0 @@
-# frozen_string_literal: true
-
-require "active_model"
-require "redis"
-
-module SuperSpreader
-  class RedisModel
-    include ActiveModel::Model
-    include ActiveModel::Attributes
-    include ActiveModel::Serialization
-
-    def initialize(values = default_values)
-      super
-    end
-
-    def default_values
-      redis.hgetall(redis_key)
-    end
-
-    def persisted?
-      redis.get(redis_key).present?
-    end
-
-    def delete
-      redis.del(redis_key)
-    end
-
-    def save
-      redis.multi do |pipeline|
-        pipeline.del(redis_key)
-
-        serializable_hash.each do |key, value|
-          pipeline.hset(redis_key, key, value)
-        end
-      end
-    end
-
-    # Primarily for factory_bot
-    alias_method :save!, :save
-
-    private
-
-    def redis_key
-      self.class.name
-    end
-
-    def redis
-      SuperSpreader.redis
-    end
-  end
-end