2019-07-18 13:35:00 UTC - Joose Helle: @Joose Helle has joined the channel ---- 2019-07-18 13:35:27 UTC - alphazero: @alphazero has joined the channel ---- 2019-07-18 23:24:34 UTC - alphazero: hi team. I am looking for a bit more detail on the state store in context of functions. Skimming the code in `instance` module it appears that the state is scoped at the broker level. The details of interest are related to the durability of the state and any f/t guarantees (for example if brokers fail over), etc. TIA. ---- 2019-07-18 23:26:25 UTC - Ali Ahmed: @alphazero state is persisted in bookkeeper and replicated so it’s durable. ---- 2019-07-18 23:28:17 UTC - alphazero: great, thanks. ---- 2019-07-18 23:34:00 UTC - alphazero: So follow up is (and I am entirely new to Pulsar and am evaluating it as a replacement for K+AMQP setup of an existing M/T SaaS system): I understand that functions can either be broker hosted or running in an external process. What is the recommended practice for (a) performance (b) reliability? ---- 2019-07-19 00:16:49 UTC - Ali Ahmed: external process are best for reliability and scale out , if you need minimum latency you want to run it within the broker as a thread. ----
