GitHub user niclash added a comment to the discussion: Pulsar Functions lifecycle and depolyment details.
Thanks a lot for taking the time to answer; Pooling; Basically, if there is dynamic creation/destruction of instances during the life-time depending on load. What you write is basically; no it is set up statically by user. Thread-safety; Everyone showcase stateless Functions and having no context it operates in. I don't find myself in that luxurious situation, and to set up the overall/over-arching context, it helps a lot to understand the exact behavior of the underlying framework. I don't really like "don't worry about it", that some systems/frameworks give. Deploy; The thing is, it is a lot simpler for me to let Ansible do the same on plenty of machines, than to do it on one. Pulsar itself sits behind firewall, so I can't reach the Pulsar APIs from my workstation, so Ansible can't execute it on localhost either. Complete; The processing in the function, letting the function return before killing it. And then there is immediately the follow up, what happens if the function has hanged? GitHub link: https://github.com/apache/pulsar/discussions/20195#discussioncomment-5766393 ---- This is an automatically sent email for commits@pulsar.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@pulsar.apache.org
