Jark Wu (@jarkwu) profile picture

Original creator of Apache Fluss, Apache Flink PMC, Staff Software Engineer at Alibaba Cloud

Hangzhou China
Joined October 2014
Thrilled to see Apache Fluss become an Apache Top-Level Project! A milestone made possible by our incredible contributors, users, mentors, and community. I’m deeply honored to be part of this journey and excited for what lies ahead. 🌊
5
393
Today's Future Data Systems Seminar Speaker: Jark Wu from @alibaba_cloud will finish off this semester with an overview of Apache Fluss. Zoom talk open to public at 4:30pm ET. YouTube video available after: db.cs.cmu.edu/events/future-…
8
55
6,921
Jark Wu retweeted
Real-time multimodal AI is finally practical ⚡️ With Apache Fluss (incubating) + Lance, you can stream data in, tier it automatically, and query it instantly for RAG, analytics, or training. Full walkthrough 👉lancedb.com/blog/fluss-integ…
3
1
15
1,387
🎉 #Fluss has reached 1,000 stars on GitHub! 🚀 This is an incredible milestone and a new beginning for our growing open-source project. A huge thanks to everyone who has contributed, provided feedback, or shown support in any way. 🌟 github.com/alibaba/fluss
2
8
823
I spent some time checking Fluss, the new streaming platform from Alibaba. Here are some findings: streamingdata.tech/p/fluss-f…
2
1
36
2,115
A wonderful experience to share streaming and meet so many friends at @FlinkForward Jakarta.
Always such a pleasure to meet fellow CDC and streaming aficionados @jarkwu and @Leonardxbj. Only at @FlinkForward Asia!
1
1
9
2,759
Open sourcing #Fluss on site of #FlinkForward Asia was an incredibly memorable experience, and it fulfilled a small dream of mine as a tech enthusiast. Join the Fluss community and build the next generation of real-time architecture together! 🚀🚀🚀 github.com/alibaba/fluss
2
2
16
1,173
The busy #FlinkForward has come to a successful conclusion, and it is an honor to share FLUSS on the Future part of Flink's 10-year anniversary. It is like Fluss returning to the birthplace of its name and taking the torch from Flink to start a new decade!
1
7
728
Stay tuned for Fluss, will back soon with more information. Read the blog if you want to learn more now! ververica.com/blog/introduci…
4
311
Really excited to share the work we've done over the past year at #FlinkForward tomorrow!
Join us at #FlinkForward Berlin 2024 for an exciting exploration into the Past, Present, and Future of Apache Flink! 🐿️ Learn exclusive ecosystem advancements and a special announcement from Ververica. ⚡Register now: hubs.li/Q02RcTnJ0 @jarkwu, @BenGamble7, @StephanEwen
1
5
834
Join us at #FlinkForward Berlin 2024 for an exciting exploration into the Past, Present, and Future of Apache Flink! 🐿️ Learn exclusive ecosystem advancements and a special announcement from Ververica. ⚡Register now: hubs.li/Q02Rdb5x0 @jarkwu, @BenGamble7, @StephanEwen
3
8
4,991
Join us for our Hong Kong Apache Flink Meetup, hosted by #AlibabaCloud on 13 June 2024. This exciting afternoon aims to deepen your understanding of streaming data with Apache Flink & Apache Paimon-based streaming lakehouse to drive greater value for your business. Register now:

1
2
6,339
Let's deep dive into the shared-storage architecture of AutoMQ(github.com/AutoMQ/automq): 1. The classic Kafka architecture, known as shared nothing, requires each broker to have a TiB-level local disk and 3 replicas. However, this setup can lead to high costs and scalability challenges in the cloud-native environment. 2. Tiered storage has indeed reduced storage costs, but the need for expensive replication and large local disks still remains. Yes, tiered storage won't fix Kafka. 3. AutoMQ's shared storage architecture utilizes EBS and S3 for shared storage. EBS functions as the WAL for recovery, while S3 serves as the primary storage. Each broker only needs a small EBS volume, making it a cost-effective solution. This design encompasses all the benefits touted by the confluent freight cluster or WarpStream, while maintaining crucial low latency for stream processing.
8
23
3
126
44,144
Apache Flink 1.19.0 is here! Packed with enhancements and new features contributed by 162 amazing individuals (including our Head of Engineering, Jing Ge!), completing 33 FLIPs and fixing 600+ issues. Huge THANK YOU to everyone involved! 🙌 Let's delve in! bit.ly/3TILNK8
1
5
11,243
Thanks Gunnar and @debezium community for the great work ❤️. Hope we can help more @ApacheFlink users and feedback more to upstream communities (mainly debezium) as well.
🗣️ "[PROPOSAL] Contribute Flink CDC Connectors project to Apache Flink" *Loving* this proposal by @Leonardxbj for making Flink CDC a part of @ApacheFlink. It's a widely used way for integrating #Debezium, and it's great to see the continued adoption! lists.apache.org/thread/o7kl…
1
17
2,632
Here are slides of another talk "Apache Flink 2.0 Preview" co-authored with @Xintong_Song at #FlinkForward 2023. We shared the planned important changes and progress of Flink 2.0. speakerdeck.com/jark/apache-…
1
7
38
3,108
Here are slides of my talk "Flink SQL: the Challenges of Implementing a Streaming SQL Engine" at @FlinkForward 2023. Hopefully, this helps you better understand the internals of Flink SQL and why building Streaming SQL is difficult. speakerdeck.com/jark/flink-s…
8
722
Great and excited to be at Flink Forward! Presented two topics about Flink 2.0 and Flink SQL internals. It's amazing to meet so many friends in person and have so many conversations about streaming data and Apache Flink! – at Seattle, WA
1
2
28
5,345