1 points | by skiniks 2 days ago ago
1 comments
Author here. We added proper app router support, SSR, and correct RSC semantics to Rari. The performance improvements were dramatic:
- 0.69ms avg response (3.8x faster than Next.js) - 20,226 req/sec throughput (10.5x higher) - 4ms P99 latency under load (12x faster) - 68% smaller bundles (27.6 KB vs 85.9 KB)
The key insight: when your architecture aligns with React's design philosophy, performance follows naturally. Server components by default, 'use client' when needed, true SSR from the Rust runtime.
GitHub: https://github.com/rari-build/rari Benchmarks: https://github.com/rari-build/benchmarks Try it: `npm create rari-app@latest`
Happy to answer questions about the architecture and how we achieved these numbers.
Author here. We added proper app router support, SSR, and correct RSC semantics to Rari. The performance improvements were dramatic:
- 0.69ms avg response (3.8x faster than Next.js) - 20,226 req/sec throughput (10.5x higher) - 4ms P99 latency under load (12x faster) - 68% smaller bundles (27.6 KB vs 85.9 KB)
The key insight: when your architecture aligns with React's design philosophy, performance follows naturally. Server components by default, 'use client' when needed, true SSR from the Rust runtime.
GitHub: https://github.com/rari-build/rari Benchmarks: https://github.com/rari-build/benchmarks Try it: `npm create rari-app@latest`
Happy to answer questions about the architecture and how we achieved these numbers.