Hi, I could not find a discussion on the new database server.
http://wiki.openstreetmap.org/wiki/New_server_and_fund_raising_drive_2013 The server that we are planning on purchasing is monster. Very complicated and expensive. I am concerned that this might not be the best way to go. We have a google summer of code proposal to write an edge proxy server for the OSM API. I don't know if the project will be accepted, but it has got me thinking about the approach and our funding drive. The idea is that each front facing server has a local snapshot copy of the OSM database to service all of the read only calls. These edge servers could be geographically distributed. It would just leave the central database server to deal with write requests, history requests, and diffs ( anything that can't be handled with a snapshot database schema). This would allow the site to scale more incrementally, and potentially scale to larger loads than putting all of our eggs into two monster servers. For the money we planning on spending on the big server, we could get could get several of these smaller edge servers with flash disks and a less expensive redundant write/history database server. As we need to scale, we can do it in 3,000 dollar increments rather 40,000 dollars increments. Having a server with 29 disks, does not seem like a good situation. Just a thought. Thanks Jason. _______________________________________________ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
