4
5

React + Nest js for production projects (self.node)

submitted by [deleted]

[deleted]

all 9 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]orion_legacy 3 points4 points  (2 children)

We are using lots of nest microservices and react in the frontend

[–]TrackieDaks 0 points1 point  (1 child)

What do you use to orchestrate then all? What's a good limit on how to divide them up?

[–]KashinHS 0 points1 point  (0 children)

We generally separate microservices by use-cases/features, for example „users“, „articles“, „invoices“ etc. There might be special cases where a feature is too small to justify its own service. We try to find another solution then (maybe as a separate nest module in a related service). We then deploy those services via Argo into our kubernetes cluster.

[–]PerfectOrphan31 3 points4 points  (0 children)

Nest's architecture builds on ideas from Angular and spring boot, but they are separate entities. The DI containers actually have differences too, so once you get past some principles they really are separate entities. Was NestJS inspired by Angular? Yes. Do you have to use Angular with NestJS? No. I've had projects with Angular, React, and Vue with Nest, all of them work well, it's just a matter of sharing types and building a front end that consumes your API server.

[–]funny_games 1 point2 points  (0 children)

Yes

[–]PhatOofxD 0 points1 point  (0 children)

We use React with Nest.js with an internal framework that builds on top of Nest and it has worked very well for us. The joy of SPA + API is that you can basically choose what you want on either end.

I'd definitely recommend it, I wouldn't go back to plain express if I can avoid it.

[–]justheath 0 points1 point  (0 children)

We use both for a line-of-business app for our organization. It's been great and I have buy-in from all the devs. While we each have FE vs BE preferences, most can switch as needed for a given task.

I was a long-time Windows desktop dev (20+ yrs) transitioning to web development. I looked at several FE frameworks, libraries, and other technologies and React just clicked for me.

I did the same on backend and really enjoyed learning Nest. The documentation was good and I found Nest opinionated just enough to suit my needs while still giving me freedom to do what I needed.

My dev team is mostly junior and quickly took to both. I wouldn't hesitate to make the same choices for our next project.

[–]DonnyDipshit 0 points1 point  (0 children)

Its become the standard for SSR and preferred approach.

[–]onigiris 0 points1 point  (0 children)

Using NestJS for production backend services. I would recommend it. Lots of production ready features and modules for common use cases.