(part 1/2)
(part 1/2)
open it to learn when:
• Kafka decides what messages are visible to Consumers
• acks=all Producers receive responses
open it to learn when:
• Kafka decides what messages are visible to Consumers
• acks=all Producers receive responses
1. 2016: KStreams targets microservices and core apps
2. ~2020: CFLT's Microservice EDA rhetoric dies down
3. 2023: CFLT goes all in on Flink
4. 2024: CFLT markets the hell out of Flink for AI & Agents (similar to microservices)
1. 2016: KStreams targets microservices and core apps
2. ~2020: CFLT's Microservice EDA rhetoric dies down
3. 2023: CFLT goes all in on Flink
4. 2024: CFLT markets the hell out of Flink for AI & Agents (similar to microservices)
The truth is clients WERE the real winner. Majority of apps are using those APIs and not much more.
The truth is clients WERE the real winner. Majority of apps are using those APIs and not much more.
The podcast is a treasure trove chock full of deep technical insights.
There is no better resource online about KIP-1150 🔥
👉 www.youtube.com/watch?v=hrM...
The podcast is a treasure trove chock full of deep technical insights.
There is no better resource online about KIP-1150 🔥
👉 www.youtube.com/watch?v=hrM...
• 2023: WarpStream launched
• 2024: Confluent bought them for $220M+
• 2025: Aiven published a KIP to the open source project to introduce the same type of leaderless, direct-to-S3 topics
• 2023: WarpStream launched
• 2024: Confluent bought them for $220M+
• 2025: Aiven published a KIP to the open source project to introduce the same type of leaderless, direct-to-S3 topics
If you enjoyed it and would like to see more, please support it by doing two simple things:
1. like
2. repost
It takes 6 seconds to do, writing this takes me 6+ hours. 🙏
If you enjoyed it and would like to see more, please support it by doing two simple things:
1. like
2. repost
It takes 6 seconds to do, writing this takes me 6+ hours. 🙏
It's "open", yes.
You could query it from any engine. You could query it from another cloud.
But you practically never will. It would bankrupt you.
It's "open", yes.
You could query it from any engine. You could query it from another cloud.
But you practically never will. It would bankrupt you.
It means that you do NOT have to spend millions in networking costs to use your data with the right engine.
You can store your data (once) in R2 and query it from anywhere, for free.
It means that you do NOT have to spend millions in networking costs to use your data with the right engine.
You can store your data (once) in R2 and query it from anywhere, for free.
Every major cloud famously charges you obscene amounts on data transfer - it's the item they make the fattest margin on.
Worse off - it's how they lock you in within their ecosystem.
CloudFlare doesn’t. 💪
Every major cloud famously charges you obscene amounts on data transfer - it's the item they make the fattest margin on.
Worse off - it's how they lock you in within their ecosystem.
CloudFlare doesn’t. 💪
But this cost isn't what matters.
The thing that makes R2 stand out is what architectures it unlocks.
But this cost isn't what matters.
The thing that makes R2 stand out is what architectures it unlocks.
Every vendor is competing at that level, because it's one of the only places where you can lock-in and extract permanent value from Iceberg users.
But I believe CloudFlare offers something that others do not (and cannot).
Every vendor is competing at that level, because it's one of the only places where you can lock-in and extract permanent value from Iceberg users.
But I believe CloudFlare offers something that others do not (and cannot).
All access goes through it, ensuring:
• thread-safe access from multiple query engines at once 👌
• single source of truth and enforcement for ACLs 🔐
• where to store data, versioning, etc.
All access goes through it, ensuring:
• thread-safe access from multiple query engines at once 👌
• single source of truth and enforcement for ACLs 🔐
• where to store data, versioning, etc.
Yesterday, they announced a managed Iceberg product: R2 Data Catalog.
It's an Iceberg REST catalog, which means it integrates natively with Iceberg-supported query engines. 🧊
Yesterday, they announced a managed Iceberg product: R2 Data Catalog.
It's an Iceberg REST catalog, which means it integrates natively with Iceberg-supported query engines. 🧊
That's when you know it won. 👑
Today - Iceberg is the standard. The only question now is how are you going to use it?
That's when you know it won. 👑
Today - Iceberg is the standard. The only question now is how are you going to use it?
An open table format. It enhances file formats like Parquet by adding extra layers of metadata that enable ACID transactions and more.
It decouples the storage layer (data) from the query layers (engines) that use it - called the headless data architecture.
An open table format. It enhances file formats like Parquet by adding extra layers of metadata that enable ACID transactions and more.
It decouples the storage layer (data) from the query layers (engines) that use it - called the headless data architecture.
R2 + Iceberg should become the de-facto choice for hybrid and multi-cloud data lakehouse architectures.
Here's why it may break the cloud monopoly 🧵
R2 + Iceberg should become the de-facto choice for hybrid and multi-cloud data lakehouse architectures.
Here's why it may break the cloud monopoly 🧵
• boost this thread by reposting to your network! 💥
I'll leave you with a Taiwan Barbet, a special endemic species you can only find in that country. 🦜🇹🇼
• boost this thread by reposting to your network! 💥
I'll leave you with a Taiwan Barbet, a special endemic species you can only find in that country. 🦜🇹🇼
Help his closest community members become Apache Kafka committers and build their careers. 👍
A 5000+ community mixing established and up-and-coming committers goes to show - one person can create splash waves in open source software. 🔥
Help his closest community members become Apache Kafka committers and build their careers. 👍
A 5000+ community mixing established and up-and-coming committers goes to show - one person can create splash waves in open source software. 🔥
Chia-Ping did all of this this while being a committer and PMC member in Apache Kafka, Apache HBase and Apache Yunikorn 🤯
Just in Kafka he’s created 600+ issues and reviewed 1,600+ commits 👀
Chia-Ping did all of this this while being a committer and PMC member in Apache Kafka, Apache HBase and Apache Yunikorn 🤯
Just in Kafka he’s created 600+ issues and reviewed 1,600+ commits 👀
The Kafka channel was super active - every day you would see discussions on 5+ different JIRAs.
The Kafka channel was super active - every day you would see discussions on 5+ different JIRAs.