Infinitic (Apache Pulsar framework for building distributed applications)
1–7 of 7 posts
Re: Infinitic (Apache Pulsar framework for building distributed applications)
#2Using kotlin on the server-side has been such a great experience.
Re: Infinitic (Apache Pulsar framework for building distributed applications)
#3Re: Infinitic (Apache Pulsar framework for building distributed applications)
#4zenaton renamed to infinitic? Is there possibility to deploy this on-premise or inside VPC?
Re: Infinitic (Apache Pulsar framework for building distributed applications)
#5Re: Infinitic (Apache Pulsar framework for building distributed applications)
#6These 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.
Re: Infinitic (Apache Pulsar framework for building distributed applications)
#7How does this compare to Cadence/Temporal ?
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.