Andrew oversees a high-demand online service processing millions of events weekly. To manage various programming languages used by engineers, from Go to Python, the team unified their processes into a single computational graph. By adopting a local-first Function as a Service (FaaS) model, they can use different languages for each node while maintaining an organized workflow. The first node employs Rust for its high performance and memory safety to successfully ingest and process events from numerous sources.
We decided to unify the entire process in one computational graph. This local-first FaaS approach allows us to use any language or tool for each node.
Rust's ownership model helps avoid memory leaks and race conditions, which is crucial when your service runs 24/7 and handles hundreds of thousands of events per minute.
Collection
[
|
...
]