|
Sounds like essentially setting up a master/slave replication, where the Armory is the master, the new DB is the slave. Since it's read-only, accessing the slave is fine. This would allow for extremely targeted crawlers from the new DB to the Armory (per battlegroup, per server, etc.).
However, once the external sites switched over...here's what I see:
- Blizzard's site becomes more responsive due to (theoretically) fewer requests, though the new DB would have more crawlers to decrease "latency" of data.
- People start crawling the new DB to replicate information to their own applications (unless you plan to open up this DB for queries)
Basically all that would happen is adding a middleman, and then you have to deal with reliability of this DB as well. Granted, crawling the new DB would be faster, as it isn't presenting web content, but raw data. I don't think we would really gain anything from such a setup.
It's a good idea, and we could probably implement it better than Blizzard, since we care more about it, but we still rely on the lacking SLA of the Armory.
|