Up to 14× faster than Vercel on live data

Click Below to Get the Code

Browse, clone, and build from real-world templates powered by Harper.

Server-side Rendering with Multi-Tier Cache

Boost your app's performance with HarperDB's multi-tier caching for server-side rendering. Achieve faster load times, live updates, and seamless reactivity across frameworks like React, Vue, and more.

Tutorial

Server-side Rendering with Multi-Tier Cache

Ethan Arrowood

Head of Open Source

at Harper

November 17, 2024

Ethan Arrowood

Head of Open Source

at Harper

November 17, 2024

Ethan Arrowood

Head of Open Source

at Harper

November 17, 2024

November 17, 2024

Boost your app's performance with HarperDB's multi-tier caching for server-side rendering. Achieve faster load times, live updates, and seamless reactivity across frameworks like React, Vue, and more.

Ethan Arrowood

Head of Open Source

‍

HarperDB’s multi-tiered caching system improves performance and reduces server load for server-side rendered (SSR) applications. The component uses caching to minimize re-renders and improve response times.

The above example showcases a blog application that uses WebSocket connections to support live synchronization of comments across clients without needing to refresh. While initial loads fetch fresh data, subsequent requests hit a cache for faster performance. This setup ensures the apps are reactive while minimizing server load.

Check out our examples that use the following frameworks:

React
‍Svelte‍
‍Vue
‍Solid

‍

INDEX

White arrow pointing right

Read the Full Story

White arrow pointing right

React SSR Example

Example of a Harper Resource Component that leverages React SSR to efficiently build and cache pages.

React SSR Example

Example of a Harper Resource Component that leverages React SSR to efficiently build and cache pages.

React SSR Example

Example of a Harper Resource Component that leverages React SSR to efficiently build and cache pages.

Icon representing link to external content

React SSR Example

Example of a Harper Resource Component that leverages React SSR to efficiently build and cache pages.

Harper Named a Sample Vendor in the Gartner® Hype Cycle™ for Digital Commerce, 2026

Harper was named a 2026 Gartner Hype Cycle for Digital Commerce Sample Vendor, recognized in Front-End Cloud for its unified runtime combining data, application logic, messaging, and agent development together.

Harper Named Winner of Two 2026 Data Breakthrough Awards

Harper has been named the winner of two 2026 Data Breakthrough Awards: Open Source Data Platform of the Year and In-Memory Solution of the Year. Harper is the only company recognized in two categories this year, reflecting its unified runtime for agentic engineering that co-locates database, vector search, cache, and application logic into a single multi-threaded process.

‍

HarperDB’s multi-tiered caching system improves performance and reduces server load for server-side rendered (SSR) applications. The component uses caching to minimize re-renders and improve response times.

The above example showcases a blog application that uses WebSocket connections to support live synchronization of comments across clients without needing to refresh. While initial loads fetch fresh data, subsequent requests hit a cache for faster performance. This setup ensures the apps are reactive while minimizing server load.

Check out our examples that use the following frameworks:

React
‍Svelte‍
‍Vue
‍Solid

‍

Boost your app's performance with HarperDB's multi-tier caching for server-side rendering. Achieve faster load times, live updates, and seamless reactivity across frameworks like React, Vue, and more.

Download

White arrow pointing right

Boost your app's performance with HarperDB's multi-tier caching for server-side rendering. Achieve faster load times, live updates, and seamless reactivity across frameworks like React, Vue, and more.

Download

White arrow pointing right

Boost your app's performance with HarperDB's multi-tier caching for server-side rendering. Achieve faster load times, live updates, and seamless reactivity across frameworks like React, Vue, and more.

Download

White arrow pointing right

Explore Recent Resources

5 Architectures for Web Personalization

Personalization is a data-delivery problem. Every architectural choice reduces to two distances: compute to user, and compute to fresh data. This piece maps five real architectures against both axes, scored on a concrete retailer workload where stale or slow data breaks the business.

Blog

Personalization is a data-delivery problem. Every architectural choice reduces to two distances: compute to user, and compute to fresh data. This piece maps five real architectures against both axes, scored on a concrete retailer workload where stale or slow data breaks the business.

Aleks Haugom

Senior Manager of GTM

5 Architectures for Web Personalization

Personalization is a data-delivery problem. Every architectural choice reduces to two distances: compute to user, and compute to fresh data. This piece maps five real architectures against both axes, scored on a concrete retailer workload where stale or slow data breaks the business.

5 Architectures for Web Personalization

Personalization is a data-delivery problem. Every architectural choice reduces to two distances: compute to user, and compute to fresh data. This piece maps five real architectures against both axes, scored on a concrete retailer workload where stale or slow data breaks the business.

5 Architectures for Web Personalization

Personalization is a data-delivery problem. Every architectural choice reduces to two distances: compute to user, and compute to fresh data. This piece maps five real architectures against both axes, scored on a concrete retailer workload where stale or slow data breaks the business.

5x Faster HNSW Vector Search with int8 Quantization

Harper 5.1 adds int8 quantization, dropping index size by roughly 3x, search throughput improves roughly 5x, and p99 latency falls from ~9s to ~0.5s under load. The tradeoff is approximately 1% recall degradation before reranking.

Tutorial

Harper 5.1 adds int8 quantization, dropping index size by roughly 3x, search throughput improves roughly 5x, and p99 latency falls from ~9s to ~0.5s under load. The tradeoff is approximately 1% recall degradation before reranking.

Kris Zyp

SVP of Engineering

5x Faster HNSW Vector Search with int8 Quantization

Harper 5.1 adds int8 quantization, dropping index size by roughly 3x, search throughput improves roughly 5x, and p99 latency falls from ~9s to ~0.5s under load. The tradeoff is approximately 1% recall degradation before reranking.

5x Faster HNSW Vector Search with int8 Quantization

Harper 5.1 adds int8 quantization, dropping index size by roughly 3x, search throughput improves roughly 5x, and p99 latency falls from ~9s to ~0.5s under load. The tradeoff is approximately 1% recall degradation before reranking.

5x Faster HNSW Vector Search with int8 Quantization

Harper 5.1 adds int8 quantization, dropping index size by roughly 3x, search throughput improves roughly 5x, and p99 latency falls from ~9s to ~0.5s under load. The tradeoff is approximately 1% recall degradation before reranking.

Vercel vs. Harper Benchmark Test

Harper runs live, personalized apps 4–14x faster than Vercel by unifying data, logic, cache, and messaging in one runtime.

Comparison

Harper runs live, personalized apps 4–14x faster than Vercel by unifying data, logic, cache, and messaging in one runtime.

Harper

Vercel vs. Harper Benchmark Test

Harper runs live, personalized apps 4–14x faster than Vercel by unifying data, logic, cache, and messaging in one runtime.

Vercel vs. Harper Benchmark Test

Harper runs live, personalized apps 4–14x faster than Vercel by unifying data, logic, cache, and messaging in one runtime.

Vercel vs. Harper Benchmark Test

Harper runs live, personalized apps 4–14x faster than Vercel by unifying data, logic, cache, and messaging in one runtime.

Agentic Engineering Needs an Opinion: Why Scale Starts with Architecture

AI coding works in a sandbox because the environment is trivially narrow. Real systems have history, constraints, and blast radius. Coding agents make sound decisions only when the architecture is explicit and shared. Opinion isn't a constraint on agentic engineering, it's what makes it possible at scale.

Blog

AI coding works in a sandbox because the environment is trivially narrow. Real systems have history, constraints, and blast radius. Coding agents make sound decisions only when the architecture is explicit and shared. Opinion isn't a constraint on agentic engineering, it's what makes it possible at scale.

Stephen Goldberg

CEO & Co-Founder

Agentic Engineering Needs an Opinion: Why Scale Starts with Architecture

AI coding works in a sandbox because the environment is trivially narrow. Real systems have history, constraints, and blast radius. Coding agents make sound decisions only when the architecture is explicit and shared. Opinion isn't a constraint on agentic engineering, it's what makes it possible at scale.

Stephen Goldberg

Agentic Engineering Needs an Opinion: Why Scale Starts with Architecture

AI coding works in a sandbox because the environment is trivially narrow. Real systems have history, constraints, and blast radius. Coding agents make sound decisions only when the architecture is explicit and shared. Opinion isn't a constraint on agentic engineering, it's what makes it possible at scale.

Stephen Goldberg

Agentic Engineering Needs an Opinion: Why Scale Starts with Architecture

AI coding works in a sandbox because the environment is trivially narrow. Real systems have history, constraints, and blast radius. Coding agents make sound decisions only when the architecture is explicit and shared. Opinion isn't a constraint on agentic engineering, it's what makes it possible at scale.

Stephen Goldberg

Building a Cozy Sandbox Game on Harper

A nature-restoration game with six biomes, 150 animals, and a real food web — built with a single Harper component as the entire backend. One YAML file wires the database, API, content seeder, and static host. The same binary ships offline on itch.io.

Blog

A nature-restoration game with six biomes, 150 animals, and a real food web — built with a single Harper component as the entire backend. One YAML file wires the database, API, content seeder, and static host. The same binary ships offline on itch.io.

Bailey Dunning

Forward Deployed Engineer

Building a Cozy Sandbox Game on Harper

A nature-restoration game with six biomes, 150 animals, and a real food web — built with a single Harper component as the entire backend. One YAML file wires the database, API, content seeder, and static host. The same binary ships offline on itch.io.

Building a Cozy Sandbox Game on Harper

A nature-restoration game with six biomes, 150 animals, and a real food web — built with a single Harper component as the entire backend. One YAML file wires the database, API, content seeder, and static host. The same binary ships offline on itch.io.

Building a Cozy Sandbox Game on Harper

A nature-restoration game with six biomes, 150 animals, and a real food web — built with a single Harper component as the entire backend. One YAML file wires the database, API, content seeder, and static host. The same binary ships offline on itch.io.

Your Website was Built for Humans. AI Needs Something Cleaner.

The web spent a decade optimizing for browsers. JavaScript-heavy rendering, dynamic CMS templates, and client-side hydration made pages beautiful and machines blind. AI answer engines retrieve, parse, and cite content directly. If your best content is trapped behind a render cycle, a cleaner source wins.

Blog

The web spent a decade optimizing for browsers. JavaScript-heavy rendering, dynamic CMS templates, and client-side hydration made pages beautiful and machines blind. AI answer engines retrieve, parse, and cite content directly. If your best content is trapped behind a render cycle, a cleaner source wins.

Aleks Haugom

Senior Manager of GTM

Your Website was Built for Humans. AI Needs Something Cleaner.

The web spent a decade optimizing for browsers. JavaScript-heavy rendering, dynamic CMS templates, and client-side hydration made pages beautiful and machines blind. AI answer engines retrieve, parse, and cite content directly. If your best content is trapped behind a render cycle, a cleaner source wins.

Your Website was Built for Humans. AI Needs Something Cleaner.

The web spent a decade optimizing for browsers. JavaScript-heavy rendering, dynamic CMS templates, and client-side hydration made pages beautiful and machines blind. AI answer engines retrieve, parse, and cite content directly. If your best content is trapped behind a render cycle, a cleaner source wins.

Your Website was Built for Humans. AI Needs Something Cleaner.

The web spent a decade optimizing for browsers. JavaScript-heavy rendering, dynamic CMS templates, and client-side hydration made pages beautiful and machines blind. AI answer engines retrieve, parse, and cite content directly. If your best content is trapped behind a render cycle, a cleaner source wins.

Get Started

No Credit Card Required.

White arrow pointing right

White arrow pointing right

White arrow pointing right

White arrow pointing right