Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RedwoodJS #134

Open
coryhouse opened this issue Jun 11, 2022 · 0 comments
Open

RedwoodJS #134

coryhouse opened this issue Jun 11, 2022 · 0 comments

Comments

@coryhouse
Copy link
Owner

Redwood is designed for startups. So their play is to get consulting for startups that use RedwoodJS.
 
Good when you’re going to have multiple front end clients (since graphql is built in)
No SSR for now but hoping to add
Mocking data is easy.
Might choose for community of startups using it. 
Doesn’t have server side power of next or remix. It’s traditional client side rendered, but can pre-render and rehydrate on client. 

Original Pitch was "Rails for JS". Also Used to be "full stack for the JAM stack". 

Redwood is no longer specific to Serverless. Can deploy to Vercel, Netlfy, EC2. 

Why Redwood over alternatives?

  • More integrated and opinionated like rails. Includes graphql and prisma storybook routing, jest security by default, declarative data fetching via cells. Everything you need to do a real startup. 

What's flexible?

Swapping out auth or deploy targets is easy. Can ignore cells. Swapping out react graphql and prisma wouldn’t make sense. They’re foundational. 
Has abstraction that allows reusing resolver logic outside of graphql.

Who's using it?

About 30 startups are using so far as of 5/2022

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant