About
Strata is a vendor-neutral technology radar for data engineering: a working catalog of the engines, storage and table formats, transformation and orchestration tools, and query and serving systems that teams use to move and model data at scale. We are not tied to any single platform — open-source and managed offerings sit side by side, batch next to streaming, mature defaults next to promising newcomers. Every entry is placed in one of four quadrants and one of four maturity rings. The aim is to give a data engineer a fast, honest bearing: what you can already build on, what is worth piloting, what to keep an eye on, and what to migrate away from.
Methodology
A ring reflects not abstract "quality" but how ready a technology is for responsible adoption: how well proven it is under real production load, how predictable it is to operate, how stable its interfaces are, and how well it fits the surrounding stack. We weigh maturity and support, availability (open-source vs managed), reproducible benchmarks, total cost of ownership, and the health of the surrounding ecosystem. The radar is deliberately vendor-neutral: neighbours in the same ring are alternatives to compare, not a better/worse ranking. Placement reflects the state of the field on the revision date and is revisited as releases ship, projects change status, and operational experience accumulates; stalled or superseded tools drift to Hold, and ones that prove themselves are promoted inward.
Maturity rings
Adopt. A mature default. Proven under real production load, predictable to operate, with stable interfaces — safe to standardise on for new and existing systems.
Trial. Ready for pilots. Production-viable and clearly valuable, but still demands real adoption effort, profile-specific tuning, or is maturing — trial it on bounded workloads with good checks before it becomes a default.
Assess. Worth watching. A promising direction with a fast-moving ecosystem or a fresh release; operational and governance patterns are still forming — explore it in isolated scenarios, not yet in critical paths.
Hold. Hold off. A stalled, wound-down, or superseded option. Not a sensible pick for new systems; keep existing deployments running and migrate off in an orderly way.
Updates
The radar is revisited as releases ship and operational experience accumulates. A machine-readable version lives at /radar.json.