Fluvio is an edge to core cloud native streaming engine built from the ground up in rust. Compiles to a single 37 Meg binary and deploys on ARM64 devices.
We just released the first public beta version of Stateful DataFlow. Stateful DataFlow is a framework for building unbounded distributed stream processing based on wasm that runs on Fluvio streams.
We are going for a Lean alternative to Kafka + Flink with a user experience of Ruby on Rails.
BTW, Stateful DataFlow has integrations with Arrow, Polars, and the ability to use SQL for dataframes, and other wasm compatible programming languages to express business logic. And Fluvio has Rust, Python, and JS clients.
Umm it's more complex than that.
Open standard would still need money to survive.
And Big Tech will flex their philanthropic muscle and influence open standards.
There is a lot of empirical evidence of this. Look at Matter protocol in home automation, GS1 in retail. Starts as a good idea but as soon as there is adoption, there will be several market motions to mess everything up.
The only way for an open standard to grow is a large extremely committed community that is largely made of people who don't have to worry about survival.
There are a lot of studies that support the rationale that blue light and apps are causing depression. It’s interesting that we are looking for solutions in apps as well.
I have got several BigTech interviews as well as jobs through regular posting long form posts on LinkedIn.
One of the best framings I have learned is to teach yourself by writing. Think of it as a conversation with your friends and you are learning together.
Take the negative comments as a motivation to improve.
My question is how do you go from posting to interviews/offers? I've been blogging for years and I do it for my own sake, but I wouldn't mind these fringe benefits.
Write a short synopsis/summary/teaser to blogs posts that are germane to work areas/technologies/languages that you'd like to work on at a future employer. Post these to LinkedIn with a link to your original long form blog post. If you know anyone who works at employers you're interested in, ask if they could pass these along as well as inquiring about what kinds of content they think would be of interest to them and others inside the organization. Do the same as above with content you discover is relevant to insiders; if you haven't already written such content, plan to make future posts on these topics, as you already know you have a target audience for such.
I'm working on this myself, for myself, as I hope to become self-sufficient and not dependent on any one employer, and also to increase the reach of content for its own sake for the benefit of all, not just a single team/group/org.
Well that's the thing... You don't. It's a very passive approach if you are actively looking for a job.
Posting solutions to interesting challenges you come across has a lot of potential getting asked to interview for jobs that solve similar problems. A generic article about "top 5 Gen AI projects" will be fruitless, but a post about how you practically "abused ramfs to make database tests 5x faster" might be.
This post prompted me to resurface the Genesis of Fluvio. We are a small team going at it for a little while since we have long relationship with the data centric applications across multiple domains for the past decades and we are excited about data streaming on rust and web assembly instead of java and jvm.
Here is a blog that is from June 2021 from our CTO laying out the vision for Fluvio.
Since the comparison question keeps popping up, I would share whatever we have as well. It's a long drawn documentation exercise and I am happy to share what we have at Fluvio.
WOW this is a big release! I want to learn more about the EBS to S3 move. What are some of the constraints and how are you managing the latency with S3?
thank you! From the beginning, we built Quickwit to work on object storage, so we worked hard to minimize the number of read requests to execute a search query. I wrote a blog post that explains the performance / costs you can obtain with Quickwit: https://quickwit.io/blog/quickwit-101
reply