| ▲ | happimess 5 days ago | |
You can have a monorepo with any tech stack you'd like. You can write your front-end and back-end in the same language. No shade to you for finding a productive setup, but Next.js tightly couples your front-end and back-end, no question. | ||
| ▲ | evilduck 5 days ago | parent | next [-] | |
> Next.js tightly couples your front-end and back-end, no question. I'd question that statement, since it's wrong. There's no requirement to connect your NextJS server to your backend databases, you can have it only interact with your internal APIs which are the "real backends". You can have your NextJS server in a monorepo alongside your APIs which are standalone projects, and Next could exist solely to perform optimized payloads or to perform render caching (being the head of a headless CMS). It seems like a weird choice to make but you could also build almost a pure SPA have have Next only serve client components. The tightness of the coupling is entirely up to the implementor. | ||
| ▲ | matt-p 5 days ago | parent | prev [-] | |
I don't use next.js really any more. That's exactly what I do. | ||