The Kafka API and S3 API have each become the de facto standard in the stream processing and object storage domains, respectively. Compared to other Kafka solutions, AutoMQ has embraced them more effectively. I believe AutoMQ has a long way to go.
Be interesting to see how well they do.<p>Most of the Kafka deployments I've seen in recent years have been using cloud versions e.g. AWS Managed Kafka.<p>So it's great that you save money on compute but it does mean you are now operating it yourself which then costs money.
Seems nice, but are there any publicly available documentation to be able to evaluate its readiness and what languages are there libraries for? I may be blind but I cannot find any.
I bet that all message queues and log databases will support S3, as these types of data generally have a large volume and aren't as economically valuable (don't get me wrong, what I mean is that these databases won't be frequently read and processed).
They're making a lot of claims and in the readme present zero measurements. The official Kafka distro is pretty bulletproof since 7+ years ago. It'd be great if they could include more information for the (apparently). initiated!<p>I am open to new things.. with at least a tad of supporting data attached :D Ymmv.
Scaling Kafka has always been a headache for me, but seeing AutoMQ storing data entirely on S3, making Brokers stateless, no longer needing to migrate data for Kafka scaling. Awesome.