# Deprecation/Removal: edx-user-state-client repo

**URL:** <https://discuss.openedx.org/t/deprecation-removal-edx-user-state-client-repo/8656>\
**Category:** Deprecation\
**Created:** [November 4, 2022, 8:06pm UTC](https://discuss.openedx.org/t/deprecation-removal-edx-user-state-client-repo/8656 "2022-11-04T20:06:22Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dave](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/dave/32/263_2.png) [@dave](https://discuss.openedx.org/u/dave)\
**Post date:** [November 4, 2022, 8:06pm UTC](https://discuss.openedx.org/t/deprecation-removal-edx-user-state-client-repo/8656/1 "2022-11-04T20:06:22Z")

</div>

**[DEPR ticket](https://github.com/openedx/public-engineering/issues/167)**

The `edx-user-state-client` repo was created to provide a common interface definition for multiple backends that could hold XBlock user state:

> **[GitHub - openedx/edx-user-state-client: Python module for storing/querying...](https://github.com/openedx/edx-user-state-client)**
>
> Python module for storing/querying user state in edx-platform. - GitHub - openedx/edx-user-state-client: Python module for storing/querying user state in edx-platform.

My recollection is that at one point [edx.org](http://edx.org) was running into scaling issues with it’s `courseware_studentmodule` table, somewhere around the point we went into the billions of rows. This repo was spun out with the idea that edX would create some more exotic storage solution (e.g. Cassandra), while leaving MySQL as the default backend.

Since that time, we discovered that the performance issues primarily came from lock contention when updating the same rows in unnecessarily long transactions, and [merged a fix that largely obviated the issue](https://github.com/openedx/edx-platform/pull/23559).

Now it’s just a shell of a repo that needs to be upgraded and maintained, with the only plausible implementation sitting in edx-platform and no future implementations planned. More recently, it’s made [a history-related PR in edx-platform](https://github.com/openedx/edx-platform/pull/31190) more difficult because it defines tests that are executed in edx-platform, and we want to change its behavior to be request-aware.

I’d like to archive this repo and transfer the interface definition back to edx-platform. Please let me know if you have any thoughts or concerns.

---

<div class="post-metadata">

**Author:** ![feanil](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/feanil/32/37_2.png) [@feanil](https://discuss.openedx.org/u/feanil)\
**Post date:** [November 8, 2022, 9:42pm UTC](https://discuss.openedx.org/t/deprecation-removal-edx-user-state-client-repo/8656/2 "2022-11-08T21:42:15Z")

</div>

This seems reasonable to me. Should there be a DEPR ticket for this?

---

<div class="post-metadata">

**Author:** ![dave](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/dave/32/263_2.png) [@dave](https://discuss.openedx.org/u/dave)\
**Post date:** [November 10, 2022, 3:41am UTC](https://discuss.openedx.org/t/deprecation-removal-edx-user-state-client-repo/8656/3 "2022-11-10T03:41:02Z")

</div>

Good point. I created the [DEPR ticket](https://github.com/openedx/public-engineering/issues/167), and I’ll move this thread over to the DEPR category. Thank you!

---

<div class="post-metadata">

**Author:** ![dave](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/dave/32/263_2.png) [@dave](https://discuss.openedx.org/u/dave)\
**Post date:** [November 30, 2022, 3:13pm UTC](https://discuss.openedx.org/t/deprecation-removal-edx-user-state-client-repo/8656/4 "2022-11-30T15:13:06Z")

</div>

I’ve moved this ticket to Accepted.
