Hi, We would like to host a separate service (logically and possibly physically) from the Flink Job which also we would like to call from our Flink Job. We have been considering remote functions via HTTP which seems to be good option on cloud. We have been considering Async I/o and statefun to use the remote HTTP based endpoint. However, we have few questions not clear for us.
1) In statefun documentation says an ingress is mandatory, so we have to define one I think? In here - https://ci.apache.org/projects/flink/flink-statefun-docs-release-2.2/concepts/application-building-blocks.html - it says `This can be anything from a Kafka topic, to a messsage queue, to an http request - anything that can get data into the system and trigger the intitial functions to begin computation.` and mentions HTTP as an ingress. However, I could not see an example on that? Can we use the statefun without an ingress or an HTTP should be the ingress to our statefun? 2) I believe https://ci.apache.org/projects/flink/flink-statefun-docs-release-2.2/sdk/flink-datastream.html is the API we have to use for calling statefun from Flink Job. However, related to question 1, how it communicates with the statefun just via HTTP? Even in that integration do we need an ingress or what will it be? 3) We are intrested in statefun for tault tolerancy, retries and etc. Also considering Async I/O for Flink I wonder if there is any pattern that we can benefit from in terms of fault tolerancy for Async I/O? If we can handle all these via Async I/O, statefun would be a heavy lifting for us. Thanks,
