I think this is the equivalent to Flink's statefun: https://flink.apache.org/stateful-functions.html

These are comparable to triggers on distributed tables under the hood, with a function addressing scheme and an ingress/egress story.

Compared to Flink, on the surface, I'd say these lack the integration with regular stream processing operators.

But anyway this is very refreshing to see! These are the future of large scale backend apps, with a clear and simple scaling path.

Interesting to see Kotlin getting more adoption in distributed systems space.

Using kotlin on the server-side has been such a great experience.

How does this compare to Cadence/Temporal ?

Infinitic and Cadence / Temporal share similar vision / objectives, but we have quite different infrastructure and architecture.

Our use of Apache Pulsar gives us an efficient foundation that is proven, scalable, and is evolving rapidly thanks to the wider community to which we belong. We have been able to inherit features such as geo-replication, horizontal scaling, transactions, tiered storage, tooling, connectors with other technologies, etc.

One of the main benefits of using Pulsar is that we can achieve high-performance, low-latency throughput with small cost infrastructure. Using Infinitic provides similar benefits than Cadence / Temporal without needing its adhoc/additional infrastructure.

zenaton renamed to infinitic? Is there possibility to deploy this on-premise or inside VPC?

Hi, Zenaton cofounder and Infinitic creator here. It's more than a renaming, it's a complete rewriting. In many ways, Infinitic is better than Zenaton. And yes you can deploy on your own :)