Reviewing the PR for an example of streaming events into Kinesis (using the embedded engine), I came to think that we could take it one step further: We could provide a ready-made main class, which configures the embedded engine based on some defined properties file (and/or environment variables), spins up the engine and keeps it running until it's stopped. The handler class would have to be provided on the classpath.

In a follow-up step, this should also expose some health check facility (e.g. using the MicroProfile API for that purpose), so that it could be monitored and restarted after failures when deployed on OpenShift for instance.

Possible outbound adapters:

• Kinesis
• CloudEvents (that's more a format and already addressed via the CE converter added in 1.1)
• NATS (Streaming)
• Google Pub/Sub