I have been intending for the Contingency Market API to operate efficiently remotely as well as locally, hence its current, rather sluggish setup my end to replicate such a use.

However, in wishing to progress a little more quickly with 1p2U, I think I’ll leave the implementation of an object cache for the CM API until a little later (given I doubt there are any API users apart from myself at the mo).

Incidentally, the CM back-end database has been designed from the outset to be bidirectionally replicatable. So that provides an alternative to achieving a similar result via the API keyhole.

As far as my immediate next steps are concerned I’m going to try out an alternative API cache, then ameliorate my deliberate server-side bottleneck, and finally migrate data processing from the page retrieval process to a background one. Page caching is another option, but I’m leaving that until last.

So, 1p2U will not change visually/functionally for a few days, despite a long list of things needing to be done.