Great read!
Jarrod Zimmerman
1

Hey Jarrod, you touched on a key point when you mentioned only the controllers interacting with the models on the server.

Having a V as part of the MVC on the backend usually represents a static, post-template rendered document. Because this doesn’t provide the opportunity for React to work its React magic on the front-end, whenever I use an MVC framework on the back-end I typically only leverage the M and C portions for handling requests and delivering a data payload based on the requests I’m listening for.

On the front-end, I use either Flux or Redux to represent the UI state, and once I inject the store with the appropriate set of data that was returned, as long as I’ve set my components to listen to the appropriate store or portion of the store, it’s all hands-off as the UI updates.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.