Harper Argues Against the Multi-System Stack and Releases 5.2
The database platform Harper advocates for a single-runtime architecture that keeps application code and data together, with its benchmark against a Vercel-based stack reporting significantly better performance on live, personalized-data workloads. Harper recently released version 5.2, with a new record cache and more throughput per node. By Renato Losio
Harper, a database platform, has argued against the multi-system stack and released version 5.2. The platform advocates for a single-runtime architecture where application code and data are kept together. A benchmark conducted by Harper against a Vercel-based stack showed significantly better performance on live, personalized-data workloads.
The Vercel stack, composed of Vercel Functions, Neon Postgres, Upstash Redis, and Ably, experienced a ~3ms network hop to a separate tier, while Harper achieved in-process data access at roughly 0.4ms. As pages pull in more personalized data, the gap between the two stacks widens. Harper's benchmark, which ran an emoji product catalog twice behind a single shared DataSource contract, demonstrated that the platform ran 474 load tests over three trials across eight scenarios and two regions in the US.
The results showed that Vercel's serverless autoscaling outperformed Harper's single free node under a high, sustained fan-out load, but the co-located runtime excelled in live data scenarios. As data freshness, scalability, cost, and complexity are all considered, Harper's approach offers several-fold improvements for live, personalized data paths, while Vercel's serverless stack shines in cacheable content and broadcast-only realtime scenarios.
Written by urgent.news from InfoQ's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
