Finally got around to reading this! Super enjoyable, and the concepts remind me a lot of @shadaj.me’s work on hydro.run and distributed stream types. Good abstractions for reasoning about distributed systems as a single program seem…pretty awesome?
I am graduating! My dissertation talk is May 16th and open to the public, will be a fun hour of recapping my work on Hydro and reflections on the experience! lu.ma/9usll5b1 (in-person priority to friends / family / mutuals)
Join us for the next SF Systems Meetup, generously hosted by OpenAI! We have an exciting pair of talks on fuzz testing and WebAssembly, you won't want to miss them: lu.ma/ltsl9g50
New Blog Post! www.shadaj.me/writing/dist... I argue that we’re *still* lacking a programming model that’s native to distributed systems, and outline what’s missing.
The SF Systems Meetup is back! On 2/27, we're excited to have headline talks from the creator of FizzBee and a research collaborator with Signal. This is going to be a super fun night diving deep into making distributed protocols work, hope you'll join us! lu.ma/vqjf30k3
Excited to share our ICDT 2025 paper on a theoretical framework to connect CRDTs and the CALM Theorem! We formalize the intuitions given in the Keep CALM and CRDT On work about the gap between CRDT guarantees and monotonic queries. arxiv.org/pdf/2502.00222
Hello! We are organizing our first South Bay Systems Coffee Chat next week. Register here: lu.ma/2f8y3fsj
(w/ @alexmillerdb.bsky.social @yingjunwu.bsky.social)
We're planning some talks in the upcoming weeks. Please follow the official account @southbaysystems.xyz 🦋 Stay tuned 👀
Hey all! Who's at POPL? If you're here and looking to do a PhD at Princeton, let's chat!
Better late than never 😂 Happy to share a recap of my SF Systems talk from last month. I've put together a summary of the session along with some great Q&A moments: www.dbos.dev/blog/sf-syst...
Thanks to the organizers and everyone who showed up—it was an amazing experience!
#dataBS #serverless
Flo itself is a theory paper, but we are actively using it as the foundation for our high-level Hydro APIs (where we use Rust types to enforce Flo properties): hydro.run/docs/hydrofl...
The goal of Flo is to be a unifying semantics, and to that end we show how the core ideas of existing systems like Flink, LVars, and DBSP work perfectly in the Flo model!
With Flo, we aim to extract the *essence* of streaming systems into formal properties: streaming progress, which formalizes keeping outputs up-to-date, and eager execution, which guarantees determinism in the face of arbitrary scheduling.
Streaming systems have broad “vibes” about responding to events in a timely manner and tolerating scheduling delays gracefully. But these “vibes” have remained informal and each system has brought its own (incompatible) set of guarantees.
Thrilled to share that our paper “Flo: A Semantic Foundation for Progressive Stream Processing” (with @mpmilano.bsky.social, Alvin Cheung, and @joehellerstein.bsky.social) will appear at POPL 2025! Check out the preprint at arxiv.org/abs/2411.08274, and read on for more!
Hey, author here, glad you found it interesting!
My talk yesterday at #SFSystemsMeetup was based on this paper. I'll share the slides soon. Thanks a lot @conorpower23.bsky.social @shadaj.me @cwensel.bsky.social and Neil for inviting me! Also thanks Jeff @ Chroma for hosting the event 💙
I'm presenting at the upcoming SF Systems Meetup! I'll dive into a new serverless architecture for stateful applications, managing function/workflow execution state using transactions. It's the research behind @dbos.dev
Register here: lu.ma/lhuuiur5 and explore more events at www.sfsystemsclub.com
