They mention all those features of databases, presenting them as important: > Databases are a nightmare to write, from Atomicity, Consistency, Isolation, and D

They mention all those features of databases, presenting them as important: > Databases are a nightmare to write, from Atomicity, Consistency, Isolation, and Durability (ACID) requirements to sharding to fault recovery to administration - everything is hard beyond belief. Then talk about their geospatial requirements, PostGIS etc, making it seems they need geospatial features ("PostGIS for geospatial data storage" -- wtf? you need PostGIS for geospatial query not merely storage...) In reality, they did not require any of the features they mention throughout the article. What a weird write-up! I guess the conclusion is "read the F*-ing specs". Don't grab a geospatial DBMS just because you heard the words "longitude" and "database" once.