Storage backed VDOM trees and hook states

Open
#1,094 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python, redis
Domain
backend, databases

Research direction

No files, tests, or entry points are named. Start by locating where VDOM trees and hook states are stored, then investigate how Redis or database-backed state could support stateless HTTP and how state eviction would work; done requires an agreed design rather than a narrowly defined patch.

Written by the indexing model from the issue text.

Description

priority-3-low type-refactor
Current Situation

All VDOM and hooks are currently stored entirely in memory. The use of additional system ram for each component could potentially be a problem for scaling an application to service hundreds of thousands of users.

Proposed Actions

One of the potential solution is to allow for VDOM and hook states to be backed by Redis and/or a database. This would allow us to create a variant of ReactPy that does not require websockets, and instead operate off the stateless HTTP.

Evicting old states becomes a challenge with these designs, but is not impossible to handle.

Dominant language
Python
Stars
8.1k
Forks
332
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from reactive-python/reactpy

All issues in reactive-python/reactpy

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.