vitedge VS rakkas-realworld

Today, Nextjs is not only cool guy in the town, A lot of meta frameworks exist like Astro, Remix. There are a few ssr frameworks also build over Vite - such as - https://vitedge.js.org/, https://rakkasjs.org/, https://github.com/frandiox/vite-ssr,

Given this situation, I think there are three solutions for my application: 1. Nuxt 3, which has support for rendering via Cloudflare Workers. 2. Cloudflare Pages, which recently got support for SSR via Workers. 3. Vitedge, which seems like a plugin for the Vite build system that targets Cloudflare Workers.

Note that we're not talking about Cloudflare Pages, which Next.js supports as a static deployment target, but actual server-rendered (well, technically speaking “edge-rendered”) React applications with support for API routes. This is a rare feature among React frameworks (I'm only aware of Flareact and Vitedge).

Vue isn't incompatible with caching, but it admittedly does need a fancier cache that runs workers: https://github.com/frandiox/vitedge is one example of such an edge-optimized thing.

I love Inertia, but it's useless for SSR. They've had an "early access" SSR for ages now, but I don't have faith it'll be ready any day soon. Separate API and UI projects are the way to go, the UI built with something like Vitedge for edge-side rendering.

Check out the updated Rakkas RealWorld Demo to see how the same full-stack application is deployed on Vercel, Netlify, Cloudflare Workers, and Node; all connected to the same Postgres database hosted on Supabase. In serverless versions, authentication requests are proxied to the Node server because CPU time limit may be too low to allow secure password hashing. They also use the Prisma data proxy for accessing the database while the Node server uses Prisma directly.

There is also a RealWorld port (Rakkas implementation of the RealWorld specification), a simple but complete fullstack application demonstrating how to approach building a REST API, accessing your database (via Prisma), handling authentication, testing, and more.

It also served as a test bed for establishing Rakkas best practices: Session management, authentication, unit testing, API testing, end-to-end testing, data validation, database access, and many other things that need to be done in a real world application has been tackled. See the github repo for a more in depth explanation of how everything works.