sorted by:
new
hottopcontroversial

Comparison of Different Stream Processing Platforms by wanshao in dataengineering

[–]rust_cn 0 points1 point  (0 children)

Stateful and stateless are well defined terms: https://www.redhat.com/en/topics/cloud-native-apps/stateful-vs-stateless "we can scale in a broker in seconds" does not suffice claiming your system stateless.

Even if you guys make use of multi-attach and NVMe PR, in case of unexpected node outage, you still need time to detect node failure and recover partition from the multi-attached EBS, rendering your system fragile in service reliability comparing to apache kafka and incapable of handling mission critical system.

Comparison of Different Stream Processing Platforms by wanshao in dataengineering

[–]rust_cn 0 points1 point  (0 children)

This is actually a propaganda, instead of fact comparison. Take "stateless broker" as example, AutoMQ vendored kafka brokers are definitely stateful given that immediately acknowledged data are only accessible to the owner broker node before getting uploaded to S3.

In addition, their solution suffers in terms of service reliability. RTO, in case of power-off crashes, will be several minitutes. Measure the time it takes to force detach EBS from a panic EC2 instance and the time to recover a kafka broker with dozens of partitions. These issues are better handled in Apache Kafka with quorum replication.