At this moment, Eventstream has no support for ingesting messages via HTTP REST / Webhook (like an Azure Function HTTP trigger). The same goes for egress to an HTTP REST / Webhook endpoint. S...
Yes, all three are useful. Regarding pulling data from a source (eg. time based) is perfect. This can lead to duplicates but this can be fixed using eg. Eventhouse materialized view. Allowing some control over the query properties would be helpful eg. the datetime of the LAST successful call. I can think of more elaborate scenarios (like a datetime from the last row from the previous message body indicating the latest messages received at that moment so no messages are missed).
