tgrez

Pulsar Functions appears to be a stream processing engine similar to Flink or Kafka Streams. In other words, it is more like a runtime for streaming apps.

The relation Pulsar ~ Pulsar Functions appears similar to Kafka ~ Kafka Streams. One is a message broker, the other a streaming engine.

Exactly-once (or effectively-once) in Pulsar Functions is depended on assigning unique sequence ids on the producer side. When consuming from Pulsar topic those can be taken from the consumed message, but AFAIK Pulsar doesn't assign those unique ids on its own, so it needs to be done externally.

Pulsar doesn't support transactions e.g. producing to multiple topics/partitions atomically.

So, you cannot have exactly-once delivery consuming from a topic and producing to another topic. Kafka starting from 0.11 supports this.

Sure, given a dev in India and a dev in SF with the same skill set, then the one in India will be willing to work for less. But when you offer a SF salary in India, then you might get a much better dev.

So, theoretically, in case of remote work and a global pool of talent, it is a less optimal use of your dollars to adjust salaries to the cost of living (all other things being equal, e.g. skill set level, culture).