GitHub user tenthe closed a discussion: Deprecate and remove the current notifications module
Currently, StreamPipes provides a built-in notifications feature consisting of: * A **notifications sink** in Pipelines * A **notifications UI module** (accessible via the top-right notification button) **Problem Statement:** There are several concerns with the current implementation: * **Limited real-world usage** Most deployments rely on external notification systems such as Email, Teams, or other integrations. * **Performance issues** When a large number of notifications are stored in the database, the UI becomes noticeably slow and less responsive. * **Questionable value** The feature duplicates functionality that is typically better handled by dedicated external tools. **Discussion Points:** * Do we still need a built-in notifications module in StreamPipes? * Is the current feature providing enough value to justify its maintenance cost? **Proposed Direction:** * Remove the notifications UI and related backend functionality * Keep the notifications sink temporarily (e.g., for one release cycle) to allow users to transition * Encourage the use of external notification mechanisms (Email, Teams, etc.) **Open Questions:** * Are there use cases where the internal notifications feature is still essential? * Would removing it break existing workflows significantly? GitHub link: https://github.com/apache/streampipes/discussions/4297 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
