---
title: "Discussion on \"Server State vs Real-Time State: Stop Putting Both in One Store\" | Hashnode"
description: "Discussion on \"Server State vs Real-Time State: Stop Putting Both in One Store\". How I split TanStack Query and Zustand in a Socket.IO chat app, and why the cache bugs and ghost typing indicators stopped showing up."
url: "https://hashnode.com/posts/server-state-vs-real-time-state-stop-putting-both-in-one-store/6ad64798548326417c19a7f6"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Server State vs Real-Time State: Stop Putting Both in One Store](https://izsk.hashnode.dev/server-state-vs-real-time-state-stop-putting-both-in-one-store?utm_source=hashnode&utm_medium=feed)

How I split TanStack Query and Zustand in a Socket.IO chat app, and why the cache bugs and ghost typing indicators stopped showing up.

Oct 19 · 18 min read · izsk.hashnode.dev  
Read the article

-   [#reactjs](https://hashnode.com/tag/reactjs)
-   [#typescript](https://hashnode.com/tag/typescript)
-   [#frontend-development](https://hashnode.com/tag/frontend-development)
-   [#nodejs](https://hashnode.com/tag/nodejs)

## Written by

[skzeeshan1992](https://hashnode.com/@izsk)

@izsk · Montreal, Canada

  
[View profile](https://hashnode.com/@izsk)

Bridging IT operations and frontend architecture through performance and system design.

Senior Software Engineer with a unique foundation in IT operations. I have spent the last 7+ years building scalable UI architectures in React and TypeScript. I focus on bridging the gap between business intent and robust code by defining cross-team API contracts, setting product roadmaps, and owning frontend architecture. My writing explores the intersection of product leadership, system design, and the realities of modern web development.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.