---
title: "Comment by Strazi Weekey on \"Building Your Own React State Management: A Deep Dive into Custom Stores\" | Hashnode"
description: "Great deep dive! As a complement, I’d suggest wrapping your custom store in a React.memo on the consumer side or using useSyncExternalStore for optimal re-rende"
url: "https://hashnode.com/posts/building-your-own-react-state-management-a-deep-dive-into-custom-stores/67d5695e0e62b5c8b6baf75a/comment/69f8a0a64f045ef8f8168d4c"
---

[Discussion](https://hashnode.com/posts/building-your-own-react-state-management-a-deep-dive-into-custom-stores/67d5695e0e62b5c8b6baf75a)

Comment [Building Your Own React State Management: A Deep Dive into Custom Stores](https://hashnode.com/posts/building-your-own-react-state-management-a-deep-dive-into-custom-stores/67d5695e0e62b5c8b6baf75a)

[Strazi Weekey](https://hashnode.com/@weekey)

[May 4](https://hashnode.com/posts/building-your-own-react-state-management-a-deep-dive-into-custom-stores/67d5695e0e62b5c8b6baf75a/comment/69f8a0a64f045ef8f8168d4c)

Great deep dive! As a complement, I’d suggest wrapping your custom store in a `React.memo` on the consumer side or using `useSyncExternalStore` for optimal re-render performance, especially in large component trees. This ensures you're not reinventing the wheel on subscription logic while still owning the state layer.