[GitHub] [openwhisk] style95 commented on issue #4993: Feature Request: Operator Defined Activation Lifecycling Events

[GitBox <gi...@apache.org>]

style95 commented on issue #4993:
URL: https://github.com/apache/openwhisk/issues/4993#issuecomment-707097804


   This generally looks good to me.
   And a couple of ideas came up.
   
   1. If you need a notification for non-blocking activation, why don't you use just blocking activation?
   Is this because the action runs for a long time, and the caller needs to work on other activities until the activation is over?
   
   2. I feel like, we need a feature similar to a callback.
   If so, I am inclined to have this functionality out of the platform.
   Instead of managing all stuff for notification, we can let users have their own notification channels.
   The platform can have a feature to call or send an event to the given channel.
   
   For example, a user can register his own notification callback URL or Kafka endpoints with a topic.
   Once activations are over, OpenWhisk will call the URL or send an event to the given Kafka.
   
   In this way, we can minimize the scope to manage.
   The failover or scalability of the channel would be managed in the scope of the external notification channel by users rather than the scope of OpenWhisk.
   
   How do you think?


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org