DEV Community

Discussion on: A JavaScript monolith ready to scale

Collapse
 
fyodorio profile image
Fyodor

Very interesting and practical approach, thanks πŸ‘

I’m curious (and didn’t find any direct answer yet), will Next bring any benefits as compared to barebones React app in case you already have an API app in (let’s say) Fastify? Does it make sense to introduce additional abstractions?

Collapse
 
joelbonetr profile image
JoelBonetR πŸ₯‡ • Edited

Hi @fyodorio it just depends on your needs.

Even if you've your services/micro-services on a different place, you can use the Server Side Rendering feature, this way your web app will be SEO-friendly.

Next Js is a framework (that implements React), so it brings a bunch of features on the top of it.

Maybe you find any feature that suits your project/s (Image or Fonts Optimisation, Routing, Static File Serving...). Also when dealing with more than a single project, using a framework can be a standard way to deal with those common tasks.

If you don't need (and analysis suggest you won't need in the future) SSR nor SSG and also you've the services somewhere else then maybe React is more suitable 😁

If it's the case and you go for React "only" I still recommend you to do a PoC with Next just to get some experience and find opportunities to use it later on.

So answering the question: Yes, it bring other sweet benefits, the question is if your specific project needs are aligned with what Next can offer πŸ™‚