State management in a GraphQL era

Dec. 9, 2017, 3:40 p.m. - 4:10 p.m.

We're going to start with exploring the evolution of making a SPA. Then we're going to dive into the problem of how fetching, caching, and reading data really complicates state-management and see what approaches we took with different libraries and frameworks like jQuery, Angular, and React.

External state management frameworks like Redux and MobX definitely helped with this problem, especially when the data is fetched from a REST endpoint.

But now that we're using GraphQL to take care of the data, is an external state-management library even needed?

Can GraphQL coexist with the other state management frameworks? What about server-side rendering? What are the pros and cons of each combination?

We'll find out what's the best way to approach this in 2017.

Kristijan Ristovski

Kitze is a developer with over 7 years of experience. He had the chance to work and experiment with a variety of languages and frameworks.

He created ok-google.io and sizzy.co, both of which skyrocketed in popularity within the first week of launch. Also he is the creator and maintainer of few popular open source libraries like mobx-router and custom-react-scripts.

His passion is to learn and teach new technologies, so he tries to share that knowledge as much as possible.

Get FrontConf event announcements

No spam, 2-3 mails per year