Hi all,
I have gone through the stateful function's documentation and required some expert advice or clarification regarding the following points. *Note: My data processing flow is as follows,* *ingress(10k/s)--> First transformation based on certain static rules --> second transformation based on certain dynamic rules --> Third and final transformation based on certain dynamic and static rules --> egress* *Questions* *1. Is the stateful function a good candidate for a system(as above) that should process incoming requests at the rate of 10K/s depending on various dynamic rules and static rules**? * 2.* Is Flink capable of accommodating the above-mentioned dynamic rules in its states (about 1500 rules per Keyed Event ) for the faster transformation of incoming streams? * *3.** I**f we are not interested in using AWS lambda or Azure functions, what are the other options?. What about using co-located functions and embedded functions? * *Is there any benefit in using one over the other for my data processing flow?* 4*.If we are going with embedded functions/co-located functions, is it possible to autoscale the application using the recently released reactive mode in Flink 1.13?* *Thanks* *Jessy*
