Post

Excited about @vite.dev's new Environments API. @canrau.com and I've been experimenting with splitting a Rakkas app into e.g. a CF Worker and a Node server where you pick which one handles which routes, kind of like Vercel's and Netlify's edge+origin setups. Envs API will make it so much easier.

2 reposts10 likes

Obviously the main server can also act as middleware: intercepting/modifying the request before proxying it to the auxiliary and/or modifying the auxiliary's response before returning to the client.

So, there will be a main server in front of any number of auxiliary servers, each potentially running on a different runtime/cloud provider etc. Main will handle some routes itself while proxying others to the auxiliaries. We have a working POC even w/o then envs API. It will be much better with it.