Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am looking to store possibly millions of spatial locations. I will need to do queries like "hotels within 10 miles of [lat,lng]".

I've had a little experience with MongoDB in this regard and was actually impressed at how easy it was. However, I'm thinking long-term and am wondering how well MongoDB would perform with giant queries like this vs Postgres/GIS.

I know maturity is a factor but it seems like most people say go with Postgres/GIS because it's mature. But is that really the best reason?

What are your thoughts? Any other alternatives like MySQL? SQL Server?

share|improve this question

closed as too localized by Ladadadada, Sven, Shane Madden, Lucas Kauffman, Evan Anderson Mar 14 '12 at 18:57

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

too localized?? – jini Jul 23 '12 at 2:39
how is this too localized? – Travis J Webb Jul 27 '12 at 22:01
yeah, too localized? wtf? – Jaka JanĨar Oct 31 '12 at 11:37