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

[User Scenario - Messaging/Eventing API] Subscribe to Kafka event and write to database #1925

Closed
dhmlau opened this issue Oct 26, 2018 · 4 comments

Comments

@dhmlau
Copy link
Member

dhmlau commented Oct 26, 2018

Description / Steps to reproduce / Feature proposal

I want to create a LoopBack 4 application that subscribes to Kafka events and then write it to a database (e.g. Cassandra).

This user scenario can be considered as the first step for the "Support Messaging/Event API" epic: #1884.

Additional Information

https://github.com/ibm-cloud-architecture/refarch-asset-analytics
https://github.com/ibm-cloud-architecture/refarch-asset-analytics/tree/master/asset-dashboard-bff

@dhmlau dhmlau changed the title [User Scenario - Messaging/Eventing API: Subscribe to Kafka event and write to database [User Scenario - Messaging/Eventing API] Subscribe to Kafka event and write to database Oct 26, 2018
@bajtos bajtos added the feature label Oct 30, 2018
@raymondfeng
Copy link
Contributor

The 1st version of the demo - https://github.com/strongloop/loopback4-example-kafka

@stale
Copy link

stale bot commented Feb 20, 2020

This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository. This issue will be closed within 30 days of being stale.

@stale
Copy link

stale bot commented Jul 14, 2021

This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository. This issue will be closed within 30 days of being stale.

@stale stale bot added the stale label Jul 14, 2021
@stale
Copy link

stale bot commented Aug 13, 2021

This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository.

@stale stale bot closed this as completed Aug 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants