[blog] Fluss rust / python / c++ client release blog draft

[leekeiabstraction]

Purpose

Draft of fluss-rust release blog.

[leekeiabstraction]

Note, links are broken because fluss-rs website is currently not up yet.

[fresh-borzoni]

@leekeiabstraction Ty, LGTM, just small comment

[luoyuxia]

@leekeiabstraction Thanks for the pr. Only left minor comments.

[leekeiabstraction]

@luoyuxia @fresh-borzoni Updated, PTAL.

I've updated blog date, and also previously missed author list (will conflict with yours Anton)

[fresh-borzoni]

@leekeiabstraction TY, looks good, couple of suggestions

Let's include list of contributors, it's a good way to say thank you for all dedicated people we are lucky to have.

Also there are a couple of things we can mention(choose whatever you think is good):

• Idempotent writes like in kafka
• Batch scanner mode, where we pass Arrow's batch directly(also we have ability to return raw Arrow with metadata), Java doesn't have this at all, but for Python's Polars/Pandas it's very beneficial, C++ plugs Arrow to DuckDB, Rust's tools also benefit from this mode. Java's clients - spark/flink have their internal row format, so not as of a big benefit, so it was never implemented.
• Memory bounded backpressure
• priority prefetch PQ for remote segments, it's more scalable than Java's. When scanning across many buckets with segments in remote storage, the parallel downloads eliminate the bottleneck of Java's single thread blocking on one segment at a time.
• pandas/polars specific API for python
• C++ support CMake/Bazel builds - it's important for C++

Also mb we need cover image, if you like - you can take otter with crab from my blog. if you like.
Also some diagrams would be good, few propositions:

• layered arch, most simple one, just to explain that there is core SDK and then bindings on top.
• batch mode - just to show how it's good for new clients that have better integration with Arrow
• PQ fetching remote segments comparing with Java(just to hint how it's different and why Rust has an edge here) - mb a bit dense, so we may prefer to skip this
• just an stylized image of all notable features of rust SDK that sells it.

[luoyuxia]

@leekeiabstraction Thanks for the pr. Left minor comments. PTAL. You may need to rebase the main branch

[leekeiabstraction]

@luoyuxia Updated, PTAL.

I think this should be ready to go today?

[luoyuxia]

@luoyuxia Updated, PTAL.

I think this should be ready to go today?

Let's wait the vote finish.
https://lists.apache.org/thread/xnk3mfjnll3k1362pyfshj5hqtf07rr3

Btw, the ci fails

[leekeiabstraction]

Btw, the ci fails

Updated, PTAL @luoyuxia

[luoyuxia]

+1. Let's merge it after we release 0.1.0 offically

[luoyuxia]

cc @wuchong @swuferhong This is release announcement for fluss client. Please help review this pr

[polyzos]

LGTM.. +1 .. let me know whether we should merge it today
@fresh-borzoni @leekeiabstraction @luoyuxia

[leekeiabstraction]

Updated blog date and minor proof read.

Eager to get this out early in the week. Should we move forward? @luoyuxia @wuchong

[polyzos]

@fresh-borzoni @leekeiabstraction @luoyuxia If there are no objections I think we can merge this today.
and maybe also #2934 ? or you want them merged in different days?
How would you guys like to proceed here?

[leekeiabstraction]

@polyzos we discussed this among ourselves

lets ship this one out first and then probably the other one early next week. This will help us ride the algo and sustain attention on the release