Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

i wouldn't say it was so good it got acquired by them, rather confluent had no s3-backed play and it was easier for them to acquire warpstream than to add it to kafka directly

warpstream has latency issues, which downstream turn into cost issues



That's a good point -- I assumed there were other choices, but now that I look, warpstream may have been the only already-kafka-compatible option.

That said, they were at least "good enough" to make "buy" more appealing than "build"


Confluent has "Freight" which is their integrated s3-backed play.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: