Skip to content

Retire Frontier and Stencil sinks #510

@ravisuhag

Description

@ravisuhag

Context

As part of the sink strategy simplification, Frontier and Stencil sinks should be retired. They are tightly coupled to specific Raystack services and serve niche use cases that the HTTP sink can handle.

Scope

  • Deprecate Frontier sink with a notice pointing to the HTTP sink as an alternative
  • Deprecate Stencil sink with a notice pointing to the HTTP sink as an alternative
  • Remove from default documentation and examples
  • Keep code available for one release cycle, then remove

Why

Maintaining dedicated sinks for niche use cases is not justified. The HTTP sink provides a generic escape hatch that covers these use cases. Focus sink investment on the Compass protocol instead.

References

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions