fission looks a great way to take functions in scripting languages like nodejs / ruby / python and turn them into HTTP services:
http://fission.io/
it'd be nice to reuse funktion's ability to deal with gazillions of different kinds of input events (salesforce, JMS, AMQP, SQS, Kafka et al...) and trigger any HTTP endpoints; then folks could use fission to write functions invoked by HTTP; then use funktion to deal with the event handling!
So we should maybe create a Subscription Manager which is a kind of Operator of event subscriptions.
e.g. you create a Subscription which is a ThirdPartyResource which defines the input event URL for email / AMQP / MQTT / NATS / Kafka or whatever, and thats bridged to one or more HTTP endpoints.
We then have a subscription operator which watches for add/update/delete of the Subscriptions and for each Subscription we create a Deployment which creates a microservice that consumes on the endpoint and invokes one or more HTTP endpoints.
Maybe once we've got this then fission could add an extra URL parameter so that a fission funktion can be exposed on both HTTP and, say, Kafka?
fission looks a great way to take functions in scripting languages like nodejs / ruby / python and turn them into HTTP services:
http://fission.io/
it'd be nice to reuse funktion's ability to deal with gazillions of different kinds of input events (salesforce, JMS, AMQP, SQS, Kafka et al...) and trigger any HTTP endpoints; then folks could use fission to write functions invoked by HTTP; then use funktion to deal with the event handling!
So we should maybe create a
Subscription Managerwhich is a kind of Operator of event subscriptions.e.g. you create a
Subscriptionwhich is aThirdPartyResourcewhich defines the input event URL for email / AMQP / MQTT / NATS / Kafka or whatever, and thats bridged to one or more HTTP endpoints.We then have a
subscription operatorwhich watches for add/update/delete of the Subscriptions and for eachSubscriptionwe create aDeploymentwhich creates a microservice that consumes on the endpoint and invokes one or more HTTP endpoints.Maybe once we've got this then fission could add an extra URL parameter so that a fission funktion can be exposed on both HTTP and, say, Kafka?