I’ve used RedwoodJS (now CedarJS) and still will for some GraphQL focused apps I have around. I always thought of old Redwood as the easiest way to get a GraphQL React app setup for success off the bat with nice deployment targets.
Now with RedwoodSDK I get the absolute easiest way to spin up a production-ready RSC app. Especially true if I don’t want to be on Vercel (I have loved Vercel’s value prop. Many old apps of mine actually still use their pro tier.)
I had already started to move pieces of apps to Cloudflare as their offerings and free tier felt insane not to take advantage of.
Cloudflare as a platform has been awesome for me:
~They have awesomely linear cost scaling. I don’t have to have mini apps to figure out when I cross tiers of usage to the same degree.
~I get a world-class CDN just there by default.
~Cloudflare charges a lot of things at a more base level which is getting more common now, but basically charging execution time not duration the worker was waiting around.
~R2, the S3 equivalent, has no egress fees so easy buy in.
~Cloudflare is already public with the infra layer there so less rug-pull fear.
~Durable Objects make stateful coordination and atomic colocation of data&compute near a user suuuuuper easy.
Then RWSDK glues it together in a way that is super AI friendly, extensible, easy to reason about because it’s just sortve handing off the req res to RSC.
I’ve almost been calling it the frameworkless framework because it just lets me do Typescript RSC. The magic is the no magic. My code does my code without crazy wiring behind curtains.
I’ve ended up with maxing lighthouse scores, deleting massive chunks of code, better seo from SSR, and feeling like I own my code. AI does amazing because then it is just writing TS functions or classes or RSC code, or Cloudflare has had pretty stable APIs / it is easy to put a few docs examples in. No making sure the AI keeps up with the new cache directive haha. (Once again I love a Vercel’s offerings, but I also love being able to surface level reason about what is happening 100% of the way through my code because of RWSDK).
I have had apps running with this for what must be a year now so can attest to stability. All problems have been me problems haha, or they were quickly rectified with awesome team.
Cool to see this live now!
A lot of things start falling into place once RSC get implemented.
Been using Redwood since v1 and started using in production since v3 now a year and a half ago and it’s been awesome framework and community to interact with.
Opinionated flexibility.
Now with RedwoodSDK I get the absolute easiest way to spin up a production-ready RSC app. Especially true if I don’t want to be on Vercel (I have loved Vercel’s value prop. Many old apps of mine actually still use their pro tier.)
I had already started to move pieces of apps to Cloudflare as their offerings and free tier felt insane not to take advantage of. Cloudflare as a platform has been awesome for me:
~They have awesomely linear cost scaling. I don’t have to have mini apps to figure out when I cross tiers of usage to the same degree.
~I get a world-class CDN just there by default.
~Cloudflare charges a lot of things at a more base level which is getting more common now, but basically charging execution time not duration the worker was waiting around.
~R2, the S3 equivalent, has no egress fees so easy buy in.
~Cloudflare is already public with the infra layer there so less rug-pull fear.
~Durable Objects make stateful coordination and atomic colocation of data&compute near a user suuuuuper easy.
Then RWSDK glues it together in a way that is super AI friendly, extensible, easy to reason about because it’s just sortve handing off the req res to RSC.
I’ve almost been calling it the frameworkless framework because it just lets me do Typescript RSC. The magic is the no magic. My code does my code without crazy wiring behind curtains.
I’ve ended up with maxing lighthouse scores, deleting massive chunks of code, better seo from SSR, and feeling like I own my code. AI does amazing because then it is just writing TS functions or classes or RSC code, or Cloudflare has had pretty stable APIs / it is easy to put a few docs examples in. No making sure the AI keeps up with the new cache directive haha. (Once again I love a Vercel’s offerings, but I also love being able to surface level reason about what is happening 100% of the way through my code because of RWSDK).
I have had apps running with this for what must be a year now so can attest to stability. All problems have been me problems haha, or they were quickly rectified with awesome team.