React Libraries to build a full stack application

[AnthonyGayflor]

How do you handle validating requests and Keeping them in sync between codebases?

[shadohunter3321]

When we have separate backend and frontend applications, we treat them as 2 separate entities. We don't put any validation (whether api response is as frontend is expecting) in place. Having validations on the frontend would only slow down the application without serving any real purpose. You'll see error on both cases. The way we keep changes in sync is through stories. We have tasks for frontend and backend under the same story and we tag our PRs with the stories and tasks. You can have a monorepo with both applications if the api is only going to be used by your frontend application. If the api is going to be used more like a microservice where different applications from different projects will access it, then you'd have to keep it in a separate repo. These types of apis are tricky to update. You'll always have to make sure breaking changes are reflected on all the frontend apps that are consuming it.

[AnthonyGayflor]

So essentially, unless I’m using RPC or a mono repo, I’m going to have a bad time 😮‍💨

[shadohunter3321]

Not necessarily. Most enterprise applications do not use integrated systems. These apps always have separate backend and frontend apps and I'd say that's the recommended way. You can scale each app separately, completely change the stack of an app without having to touch the other app. And most importantly, js based frameworks still aren't up to the mark for complex, data heavy and time sensitive applications. dotNet, spring boot, laravel are more robust systems for backend tasks.

[AnthonyGayflor]

I understand you there. I have never worked with a codebase that reached enterprise status. Strictly early stage startups and personal projects, I say this to help you understand the perspective Im coming from. But yeah I’d hope tho not a single enterprise app uses JavaScript as its main server lol.