# The future of state management

DevFeed: [The future of state management](<https://devfeed.tech/articles/the-future-of-state-management-23538.md>)

Original publisher: [Read original article](<https://www.apollographql.com/blog/the-future-of-state-management-dd410864cae2>)

Author: Peggy Rayzis

Published: 2017-12-21T22:36:00Z

Content type: article

Language: en

Sources: [Apollo Blog](<https://devfeed.tech/sources/apollo-blog.md>)

Topics: [apollo-client](<https://devfeed.tech/topics/apollo-client.md>), [GraphQL](<https://devfeed.tech/topics/graphql.md>), [Redux](<https://devfeed.tech/topics/redux.md>)

Tags: [announcement](<https://devfeed.tech/tags/announcement.md>), [apollo-client](<https://devfeed.tech/tags/apollo-client.md>), [data](<https://devfeed.tech/tags/data.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [redux](<https://devfeed.tech/tags/redux.md>), [state](<https://devfeed.tech/tags/state.md>), [state-management](<https://devfeed.tech/tags/state-management.md>), [ui](<https://devfeed.tech/tags/ui.md>)

## AI overview

The article discusses managing both remote and local application state with Apollo Client. It describes the limitations of maintaining separate Redux or MobX stores and presents GraphQL queries and mutations as a way to represent application state and combine data from local and remote sources.

## Source excerpt

When an application grows in size, its state often grows in complexity. As developers, we're not only tasked with juggling data from multiple remote servers, but also with handling local data resulting from UI interactions. To top it off, we have to store all of this data in a way that's easily accessible from any component in our application. Thousands of developers have told us that Apollo Client excels at managing remote data, which equates to roughly 80% of their data needs.