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

Publisher Subscriber support #155

Open
avara1986 opened this issue Sep 24, 2020 · 0 comments
Open

Publisher Subscriber support #155

avara1986 opened this issue Sep 24, 2020 · 0 comments
Labels
feature New feature in progres Hacktoberfest help wanted Extra attention is needed

Comments

@avara1986
Copy link
Member

Not all microservices are RESTful service. A common use case is read and/or write information form a queue. A simple solution (and in most case, the best solution) to retrieve data from a queue is a serverless solution like AWS Lambdas or Google Cloud Functions. But, imagine that: you must have a stream of data, and a heavy processing (more than 5-10 minutes) and this process must run in a Kubernetes cluster. In this case, you need a main process with an healthcheck (or status, or metrics) endpoint and other process listening a queue.

Steps:

  • Create a Driver patter like Crypt Driver to support multiple queues systems (Redis; SQS, PubSub, Kafka, AMP, AMQP...)
  • This Queue must run in a different process of main Flask application
  • Update the main class Microservice to search for a Queue Resource
  • Create a blueprint like Healthcheck to get information of the queue (status, pending messages, errors...)
@avara1986 avara1986 added help wanted Extra attention is needed feature New feature in progres Hacktoberfest labels Sep 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature in progres Hacktoberfest help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant