A writer given to puns might say that web-frontend data architecture is in a state of flux right now.

Two-way data binding was no panacea and functional, immutable, one-way data flow is the hero of the day. But there are a lot of details that still have to be figured out. For instance:

  • how do we deal with async data on the server?
  • should state mutation logic live with the components or in a central location?
  • how do different routes affect what data we keep in the central store?

This issue is dedicated to resources that answer some of these questions.

Redux is the dominant library for the moment, but there are tons of ideas on how to improve redux (see redux-saga below). Furthermore, server-sync tools like Relay aren't compatible with the current form of redux, so we'll surely be seeing more evolution of these patterns in the coming months.

Fair warning: I'm a bit obsessed with webapp data architecture at the moment, so we'll definitely be covering this sort of thing again, albeit in a new light. Traditional MVC isn't quite working for webapps and we're all trying to figure out what does.




Data Architecture


Like what you've been reading from Fullstack React? You can help us spread the word. Please forward this email to you friends (and let them know they can subscribe here).

Follow us on Twitter

Curated with love by Nate Murray and the Fullstack.io team.

Suggestions are welcome, just reply to this email - we'd love to hear from you.