Hey, thanks for the mention! I'm the creator of Nodewood, and I'm happy to answer any questions anyone has on it, or really anything else in the space I can help with. Source: over 3 years ago

This is largely why I built Nodewood [1]. Every time I wanted to start a new project, almost always a SaaS idea, I'd skip over the "boring stuff" like building user management, subscription management, teams, admin, all that, to get to the meat of the business logic, to make sure I had a valid idea. But I still needed all that stuff eventually, so I'd have to lose time later building it all in! So I decided to... - Source: Hacker News / about 4 years ago

This is actually part of why I created Nodewood [1], because every new Node project required pulling all that together, and every new SaaS idea I had had the same basic requirements (user management, subscription management, teams support, etc). Then I figured, if I found this useful, surely others would too, so I packaged it up and have had a few happy customers since then, who have helped me refine it, which... - Source: Hacker News / about 4 years ago

Well, I've spoken about this before, and on here no less, but only really in response to posts like this. I don't do any advertising or speak about mine except in interviews, since it's usually indicative of the kind of requirements they're looking for. I created a SaaS bootstrap for Javascript called Nodewood [1]. It actually started as just a template for me, because there's a lot of setup for each new JS web... - Source: Hacker News / about 4 years ago

Disclaimer: I'm the author of the following boilerplate. Nodewood (https://nodewood.com/) is a Javascript SaaS boilerplate built to take advantage of using Javascript on the server and in the UI. Models, Validators, and other business logic can be re-used in both builds, so you don't have to write, rewrite, and maintain that logic in both places, or in different languages. It has built-in subscription management... - Source: Hacker News / over 4 years ago

For example, Netflix DGS provides @DgsDataLoader annotations in Java, gqlgen documents DataLoader integration for Go, and GraphQL-Ruby has GraphQL::Dataloader built in. Query compilation engines (Hasura, PostGraphile) bypass the need for DataLoader by generating optimized SQL directly. - Source: dev.to / 4 months ago

In our Rails application, we use the popular graphql Ruby gem to resolve GraphQL queries. When used naively, it essentially resolves queries as a depth-first tree traversal, which leads to the N+1 problem in GraphQL. - Source: dev.to / almost 4 years ago

If you're comfortable on the react/client side with graphql, I'd highly recommend plugging in https://graphql-ruby.org/. Source: about 4 years ago

The next step is to add the GraphQL gem to our Gemfile; you can visit its page, graphql-ruby, for more details; now, open your Gemfile and add this line:. - Source: dev.to / over 4 years ago

If you do go the API route though, strongly consider using GraphQL with the (graphql-ruby)[https://graphql-ruby.org/] gem. Source: over 4 years ago