Over the past year, I’ve been building a new full-stack web framework from the ground up — one that doesn’t rely on Node.js, Webpack, or the typical JavaScript ecosystem. Instead, it’s built on two compiled languages working together:
- Dart (NevaehUI) for the frontend
- Crystal (KothariAPI) for the backend
The combined framework is called Dartalyst, and based on internal benchmarks, it now ranks among the fastest SSR frameworks currently measured.
This post breaks down the numbers, the comparisons, and why this architecture works — with public testing opening in 3 weeks.
🚀 SSR Benchmark Results
Dartalyst was tested across four workloads:
| Test | Throughput |
|---|---|
| Simple SSR | 30,937 req/s |
| Concurrent SSR | 25,897 req/s |
| Complex Components | 7,029 req/s |
| Data Fetching (SSR) | 6,887 req/s |
All tests included:
- HTML generation
- Component rendering
- State serialization
- Hydration markers
- Real routing logic
No caching.
No pre-rendering.
Just actual SSR.
📊 How Dartalyst Compares to Established SSR Frameworks
Below is a comparison using publicly available SSR benchmark ranges (not raw HTTP benchmarks).
🥇 Top-Tier SSR (20,000+ req/s)
| Framework | Approx. SSR Throughput |
|---|---|
| Dartalyst | 30,937 req/s |
| Bun SSR | 15,000–30,000 |
| Qwik | 10,000–25,000 |
Dartalyst lands at the top of this tier.
🥈 High-Performance SSR (5,000–15,000 req/s)
| Framework | Approx. Throughput |
|---|---|
| SolidStart | 8,000–15,000 |
| SvelteKit | 7,000–12,000 |
| Preact SSR | ~2,052 |
🥉 Mainstream SSR (1,000–5,000 req/s)
| Framework | Approx. Throughput |
|---|---|
| Next.js | 2,000–7,000 (React 19 SSR ~572) |
| Remix | 3,000–8,000 |
| Nuxt (Vue 3) | 2,000–6,000 |
| Angular SSR | 3,000–6,000 |
| Astro | 2,000–5,000 |
⛔ Low-End SSR (< 1,000 req/s)
| Framework | Approx. Throughput |
|---|---|
| Laravel SSR | 1,000–3,000 |
| Rails SSR | 500–2,000 |
| React SSR (Node) | ~366 |
| React SSR (Bun) | ~650 |
| React SSR (Deno) | ~601 |
🎯 Final Ranking (Technical, Not Marketing)
Based strictly on available data:
Dartalyst is currently in the top 3 fastest SSR frameworks measured — competitive with Qwik and Bun SSR, and faster than most mainstream SSR frameworks (Next.js, Nuxt, Remix, SvelteKit, Angular, etc).
This is actual SSR performance, not HTTP echo servers.
🔧 Why Dartalyst Performs So Well
Because the entire stack is compiled, not interpreted.
NevaehUI (Dart)
- Compiler-based rendering
- No virtual DOM
- Tailwind-style utilities
- Hydration only where needed
KothariAPI (Crystal)
- Native binary backend
- Rails-inspired routing + models
- Low-latency HTTP stack
Dartalyst (Full-Stack Layer)
- Shared routing
- Full SSR pipeline
- Unified CLI
- No Node.js
- No Webpack/Vite
- Minimal runtime overhead
The result: very high throughput under load.
⏳ Public Testing Opens in 3 Weeks
The first public release (v0.1.0) will be available between December 15–22, 2024.
It will include:
- Full SSR
- Hydration
- Template rendering
- Project scaffolding
- NevaehUI components
- Crystal backend
- Basic documentation
- Example apps
You’ll be able to benchmark it yourself.
🔮 What’s Next
- v1.0.0 release (Jan 2025)
- Streaming SSR
- More templates
- Security hardening
- Documentation site
- Community packages
- Official benchmark suite
✔️ Final Thoughts
Most web frameworks today are slowed down by:
- virtual DOMs
- JavaScript hydration
- layered toolchains
- runtime overhead
Dartalyst shows what’s possible when you remove all of that and build a full-stack SSR system from two compiled languages.
If you want to follow the release or run benchmarks yourself, keep an eye out — early access drops in 3 weeks.
Top comments (0)