> One of our lead engineers setup an NX monorepo. We deploy an API to AWS and our front-end to vercel.
I don't understand where the complexity is in your setup that you're unhappy with.
I don't understand where the complexity is in your setup that you're unhappy with.
Furthermore, in our case, the front-end and backend are really coupled, so having these as separate systems is just a big headache. All of the web app's views are tied into specific backend functionality, and our API doesn't really stand on it's own without the front-end.
Yes this is poor architecture. I'm just pointing out a case where JAMStack was a mistake. Rails (or similar) would have been a smarter choice.
If you want more coupling, perhaps you could try something like ts-rest to add API types to your frontend. Or if you're feeling more adventurous, GraphQL or tRPC, though I personally prefer to avoid being tied to overly experimental frameworks.
Next.js has saddened me since the move to SSR. I think remix is light-years ahead to be honest.
I will give ts-rest a look-see.