Ask HN: Which framework do you use for your APIs (Node.js or Ruby)

1 points by vixalien ↗ HN
I'm using NextJS (Serverless React on Node.JS) but the api structure there is very limiting, especially considering Ruby on Rails. I was looking for an API framework that can handle pretty expensive business-level workloads maybe in Node.JS or Rails. I wanted to go with Rails, but I'd be severely losing on Serverless (I use Vercel to host). If you have any idea, you're welcome. tya.

8 comments

[ 3.8 ms ] story [ 34.4 ms ] thread
If you workload is "expensive" you want to use a language that is more static like Java or Go.
I have used Java in the past and with all the horrors I've seen there, not going back.

I have considered trying Go but I don't know how it will deal with the whole serverless stuff.

NestJS for node works quite well for APIs (TypeScript as a bonus).
Have you looked at Ruby on jets.

Serverless framework for ruby: https://rubyonjets.com/

Yeah, I did. The only reason I couldn't use it is it doesn't support MongoDB, which I use.
Maybe Webiny (https://www.webiny.com, https://www.webiny.com/docs) could be the solution you're looking for! ;)

It's designed to make serverless application development as easy as possible.

For example, with the built-in scaffolds (https://www.webiny.com/docs/how-to-guides/scaffolding/introd...), you can pretty quickly provision a new React application, GraphQL API, or even a full-stack application. Once that's up, further development is as easy as simply starting a new watch session with the "webiny watch" command (https://www.webiny.com/docs/how-to-guides/use-watch-command/). It will make sure that all of the changes that you perform, both on application and cloud infrastructure code level, are automatically deployed into the cloud for you. In a way, this mimics the good-old local development experience.

And there's a lot more, but I'd probably pollute the thread. :)

If you're interested, feel free to ping me, here or maybe via our community Slack (https://www.webiny.com/slack). I'd be glad to assist with any questions / feedback you might have.

@vixalien

P.S. Disclaimer: I work at Webiny :)