Data Conflicts - last missing feature in evolution of GraphQL?

By Wojciech Trocki

Elevator Pitch

Caching data is hard. Invalidating modifications made on cached data can be even harder. In this talk we going to demystify how to handle data conflicts in GraphQL and share the best patterns that can be applied to every GraphQL implementations.


In this talk we going to focus on efficient ways to modify GraphQL transport in order to detect and manage application conflicts. Author is going to cover best patterns for detecting conflicts in separation from data store, methods of notifying clients about conflicts and effectively managing and updating the client cache along with conflict resolution policies that can be added to automatically manage conflicts without user interaction.


In talk I’m going to cover technical aspects of conflict resolution mechanism based on open source library that will provide this functionality out of the box. Going to update submission with blog post and additional material over the coming weeks.