Raven Analytics
Rust · Polars · AWS · data correctness
A cheaper pipeline still has to produce the right answer.
I rebuilt a Python-on-EC2 analytics pipeline in serverless Rust and Polars. The measured workload ingested more than 2 GB of events a day, with roughly 90% less compute spend than the previous implementation.
For validation, I reconciled daily row counts exactly, checked column-level counts over matching date ranges, and investigated discrepancies against source logs. That work uncovered duplicate events in the original data.
These results describe that workload and comparison, not a guarantee for every analytics system. Raven is a product of my company, math.technology.
Explore a related correctness example
The synthetic daily brief below demonstrates the same principle: every number should have a definition, source and limitation. It is a new offline example, separate from the production migration.