The blog post mentions that partitions are too low-level an abstraction to program against. Does that mean WarpStream doesn't use partitions?
Do you provide any ordering guarantees like Kafka does at the partition level?
Do you provide any ordering guarantees like Kafka does at the partition level?
That's all required to build exactly-once systems on top of Kafka (like the stateful stream processing engine I work on) even if it's not the easiest interface for normal application-level development.
WarpStream is Kafka protocol compatible, so we do support topic-partitions and consumer groups. We do not expose support for transactions or idempotent producing today, but the internals of the system support that and we will probably work on the idempotent producer sometime in the next month, with transactions coming shortly after, depending on demand from the Developer Preview users.