Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consolidate the control plane implementations #24

Open
wkerckho opened this issue Jul 5, 2022 · 3 comments
Open

Consolidate the control plane implementations #24

wkerckho opened this issue Jul 5, 2022 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@wkerckho
Copy link
Contributor

wkerckho commented Jul 5, 2022

There are various components that use control signaling for triggering actions across the micro-services. For example:

  • The Catalog service uses a Pulsar topic to schedule data exports.
  • A Redis-based session manager component is used to remotely close data streaming sessions (SSE).

It does not make sense that the platform has different ways of implementing control signaling and these approaches should be consolidated.

@wkerckho wkerckho added the enhancement New feature or request label Jul 5, 2022
@wkerckho wkerckho self-assigned this Jul 5, 2022
@MisterTimn
Copy link
Contributor

So for our specific case we should choose between Redis and Pulsar or more ideally between using the MessageBroker abstraction being introduced through #22 and the Redis abstraction for #23?

Or would this ideally be a third abstraction?

@wkerckho
Copy link
Contributor Author

Because use of control messages is limited, I would indeed propose to choose one of the abstractions.

@github-actions
Copy link
Contributor

The issue had no activity for 30 days, mark with Stale label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants