Improve how synchronization is done about chihaya HOT 3 CLOSED

I feel like this and #2 are the same thing. If you feel up for installing redis after the server transfer tomorrow and then make a test similar to how gazelle would publish to redis if it was monkey patched, we can sort out this section of the code. Then when Batter comes around, we only have to adjust the database package and the redis schema; the synchronization will be solved.

from chihaya.

We could actually just go ahead and implement the pub/sub part of redis in Batter.

from chihaya.

In the new architecture, everything is stored via the Storage interface and when the tracker wants any information, it simply uses the Storage interface as an abstraction to query/update the data store. There is no cache and, if there was in the future, I wouldn't want it to depend on pub/sub functionality of the data store to keep it from becoming stale. Transactions/locking of the storage resources are left as an implementation detail of storage drivers.

from chihaya.