Contents

# Optimization

One optimization that flipper provides is a memoizing middleware. The memoizing middleware ensures that you only make one adapter call per feature per request.

This means if you check the same feature over and over, it will only make one Mongo, Redis, or whatever call per feature for the length of the request.

You can use the middleware from a Rails initializer like so:

```ruby
# create flipper dsl instance, see above Usage for more details
flipper = Flipper.new(...)

require 'flipper/middleware/memoizer'
config.middleware.use Flipper::Middleware::Memoizer, flipper
```

If you set your flipper instance up in an initializer, you can pass a block to the middleware and it will lazily load the instance the first time the middleware is invoked.

```ruby
# config/initializers/flipper.rb
$flipper = Flipper.new(...)

# config/application.rb
config.middleware.use Flipper::Middleware::Memoizer, lambda { $flipper }
```

**Note**: Be sure that the middleware is high enough up in your stack that all feature checks are wrapped.

Version data entries

9 entries across 9 versions & 1 rubygems

Version	Path
flipper-0.7.5	docs/Optimization.md
flipper-0.7.4	docs/Optimization.md
flipper-0.7.3	docs/Optimization.md
flipper-0.7.2	docs/Optimization.md
flipper-0.7.1	docs/Optimization.md
flipper-0.7.0	docs/Optimization.md
flipper-0.7.0.beta6	docs/Optimization.md
flipper-0.7.0.beta5	docs/Optimization.md
flipper-0.7.0.beta4	docs/Optimization.md