To address this issue, it is important to identify the following:
[x] Which events are important to track (Task registration/unregistration, node subscriptions, created stacks, disputes, etc);
[x] Which database is more suitable for our purposes (possibly a combination of Redis for cache memory and PostgreSQL);
[x] How much up to date Stacks the proxy is currently managing, and how many compute units it has available across tasks.
[x] Which nodes have been assigned to which Stacks, so the proxy can query these when necessary. This includes keeping a record of up-to-date nodes public urls (for now).
To address this issue, it is important to identify the following:
Stacks the proxy is currently managing, and how many compute units it has available across tasks.Stacks, so the proxy can query these when necessary. This includes keeping a record of up-to-date nodes public urls (for now).