I have had a single server in production for more than a year, but I'm reaching the point where I need additional server instances to handle the load. The problem I'm trying to solve is my use of context. I have a database with a list of devices. New devices may be added or removed, or their properties may be updated. Since the admin web page that makes such changes is hosted on the sole server instance, I can trigger the device list to be loaded after changes are applied.
With multiple instances I can't do this any longer because the device list on one server will get updated, but the other server(s) will not receive the update event. I suppose I could call out to the other servers with a web service to force an update, but then I would need awareness of other servers, which seems like a brittle solution.
Or, I could poll the database for changes in the device list, but this has a cost and there will still be some lag time before the servers are in sync.
An easy solution would be to use the contextStorage property to have context stored in a database. Unfortunately, there is no contextStorage support for databases (I use MongoDB).
What are others doing to solve this problem?