How flippercloud/flipper works
Main components
• Core Library (lib/flipper):
• DSL & Configuration (Flipper, Flipper::DSL, Flipper::Configuration)
• Feature & Gate Model (Flipper::Feature, Flipper::Gate, Flipper::Gates::* classes)
• Expression Engine (Flipper::Expression::Builder & expression classes)
• Adapter Builder (Flipper::AdapterBuilder)
• Instrumentation (Flipper::Instrumentation, Instrumenters, Subscribers)
• Exporters (Flipper::Export, Exporters::JSON)
• Adapters (lib/flipper/adapters/*):
• Built-in: Memory, ActiveRecord, Redis, Moneta, PStore, Mongo, Sequel, HTTP, etc.
• Adapter Wrappers: Memoizable, Instrumented, Failover, Sync, Cache base, etc.
• REST API (flipper-api gem):
• Rack Middleware (Flipper::API::Middleware)
• JSON endpoints (lib/flipper/api/v1/actions & decorators)
• UI (flipper-ui gem):
• Rack App / Engine (Flipper::UI)
• Views & Assets (ERB templates, CSS/JS)
• Actions & Decorators
• Cloud Integration (flipper-cloud gem):
• Cloud DSL & Config (Flipper::Cloud::Configuration, DSL)
• Middleware & Routes
• Telemetry & Backoff (Flipper::Cloud::Telemetry)
• CLI (exe/flipper, lib/flipper/cli)
• Generators (lib/generators/flipper)
• Examples & Benchmarks (examples/*, benchmark/*)
Relationships & data flows
• Application code → uses → Flipper DSL/API → checks/enables/disables features
• Flipper Core → delegates → AdapterBuilder → selected Adapter → persists/reads flags from external store (DB, Redis, etc.)
• Instrumentation wrappers around Adapters → emit metrics/logs → Instrumenters/Subscribers
• Exporters → read from Core → output JSON, GZIP
• flipper-api middleware → receives HTTP requests → invokes Core → returns JSON
• flipper-ui Rack app → web UI → uses Core (through DSL/API) to display & modify flags → persists via Adapter
• flipper-cloud middleware → synchronizes Core with remote Cloud service → uses HTTP adapter under the hood → Telemetry & Backoff
• CLI → invokes Core & Exporters → outputs to STDOUT or files
• Generators → scaffolding for Rails apps → create initializer & migrations
Architectural patterns & principles
• Adapter Pattern: Core is adapter-agnostic; adapters plug in to support any data store
• Middleware Pipeline (Rack) for both API & UI
• DSL for expressive, Ruby-friendly feature checks & configuration
• Strategy Pattern for expressions & gates
• Separation of concerns:
• Core logic vs. persistence (adapters)
• UI vs. API vs. Cloud sync vs. CLI vs. Generators