A streaming data-flow system that acts as a fast storage backend for read-heavy web applications by precomputing and caching relational query results.
Noria is a streaming data-flow system that functions as a high-performance storage backend for read-heavy web applications. It precomputes and caches the results of relational SQL queries as materialized views, which are automatically updated as data changes, delivering fast reads and high write throughput. It solves the performance bottleneck of traditional databases for dynamic, data-intensive web services.
Developers and engineers building read-heavy web applications, such as social platforms, news aggregators, or real-time dashboards, who need sub-millisecond read latency and high scalability without manual caching complexity.
Developers choose Noria because it offers database-like durability with cache-like speed, automatically maintaining materialized views through incremental data-flow. Its MySQL adapter allows easy integration with existing stacks, and its partial-statefulness reduces memory overhead compared to full materialization.
Fast web applications through dynamic, partially-stateful dataflow
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports runtime changes to data-flow and queries without downtime, allowing flexible adaptation to evolving application needs as per the key features.
Uses partially-stateful data-flow to significantly reduce memory overhead, making it scalable for large datasets without full materialization costs.
Comes with a MySQL adapter implementing the binary protocol, enabling existing applications to switch with minimal effort, as highlighted in the README for easy integration.
Precomputes and caches relational query results as materialized views, turning reads into fast lookups with up to 5x throughput improvement shown in Lobsters benchmarks.
Requires Apache ZooKeeper for coordination and nightly Rust for building, adding deployment overhead and potential instability due to reliance on cutting-edge tools.
Focused on parameterized queries for materialized views, lacking full SQL-92 compliance or advanced transactional guarantees compared to traditional databases.
As a research project from MIT, it has a smaller community, fewer production-ready tools, and less documentation than established databases like PostgreSQL or MySQL.