Explore >> Select a destination
|
You are here 
|
www.confluent.io | ||
| | | | |
compositecode.blog
|
|
| | | | | I've worked with (** references at end of article) a number of Apache projects over the years, often pretty closely; Apache Cassandra, Apache Flink, Apache Kafka, Apache Zookeeper and numerous others. But the last few years I've not been immediately hands on with the technology. A few questions popped up recently, that fortunately I was... | |
| | | | |
www.decodable.co
|
|
| | | | | At Decodable, we have long believed that Apache Flink is the best stream processing system, with a proven track record of meeting the demands of some of the largest and most sophisticated businesses in the world, such as Netflix, Uber, Stripe, and many more. We are excited to welcome Confluent to the ranks of companies, like ourselves, who regard Flink as the industry standard for meeting the real-time stream processing needs of businesses, large and small. | |
| | | | |
streamnative.io
|
|
| | | | | Ursa: Reimagine Apache Kafka for the Cost-Conscious Data Streaming | |
| | | | |
www.onehouse.ai
|
|
| | | AWS S3 Tables aims to simplify Apache Iceberg table maintenance, but we found long compaction delays, limited observability, and costs 20-30x higher than alternatives. Delays of 2.5-3 hours hurt performance, and S3 Tables lack controls over compaction frequency or performance profiles. | ||
