Skip to content

There should be a complex example of a service based rollout and subscriber #5

Description

@jejacks0n

The general idea is to provide an example for others to use when writing their own gems if they want to. I think using Unleash for this would make the most sense, but using something like LaunchDarkly might also be useful.

Things that should be built in to the subscriber:

  • Metrics on as much as possible -- variant resolution, callback times, etc.
  • Include details to understand the variant resolution lifecycle.
    • Assigned manually before run?
    • Set manually in the run block?
    • Set in a run callback? (before and around)
    • Resolved through the cache?
    • Resolved through segment rules?
    • Resolved through the rollout?
    • Was the variant cached?

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentationenhancementNew feature or request

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions