OpenStreetMaps - tiles - performance issues for heavy use
I am working on a mobile app that will be mostly map based. I am new to map development. Basically my app will use markers and some custom controls to allow users to navigate to some pages / popups to show some details / links to other features. Its NOT going to use navigation or "search nearby" or post features. But the map view will be the main view for users (sort of like a "waze" application, the main functionality of which is in the "Maps" view). Therefore, I expect to see a lot of traffic on my maps screen.
Since Google starts charging for apps beyond the threshold, I plan on using the open source API. and tiles from openStreetMap. http://www.openstreetmap.org/
My question is, if my userbase is going to go up (for example, waze has around 2.6 million users), I have to worry about the openStreetMap tiles being scaled up to this heavy traffic. Will it scale nicely or will it cause performance issues?
While I am trying to contact OSM with my above question, I thought about asking this question here and on SO, appreciate if the map developers can share their experience with this API-Tile combination and / or if you have any other guidance / suggestions / recommendations for the development of maps.
source to share
Here you have the official OSM tile policy . You can also take a look at the list of OSM web hosting providers .
source to share
Use Bing Maps, they have a limit of 50,000 transactions in 24 hours , I doubt even Waze has that many in the US).
source to share
I think you will be fine with OSM slabs. If you have a very large number of users, you might want to look at Mapbox , which compares to Google Maps for competitive prices, as Foursquare and Airbnb, for example, switched from Google Maps to Leaflet and Mapbox. They also have very good maps and most of their tools are open source.
source to share