A mobile Internet application map service architecture

In the mobile Internet, a variety of location-related services are heavily dependent on the map service, the quality of the map service largely determines the level of service provided. Notwithstanding the availability of free or paid map services such as Google Map, none of the map service providers is fully mobile http://www.aliyun.com/zixun/aggregation/11969.html "> Internet applications must Various map services and data, especially for those vertical industry applications.

Under the system of Chinese characteristics, besides the technical factors, it is noteworthy that the impact and challenge to the architecture achieved by the policy uncertainty caused by the issue of the map license.

Map service architecture design principles:

1, high performance: As the current mobile Internet bandwidth is still a greater constraint, waiting in the client user limited patience, so the map service must be the performance of the primary design elements. And like Google Maps like free services due to the firewall often unstable or unusually slow, you need to focus on architectural design.

2, low-cost: Although some of the paid map service has provided some more complete map data, POI data, but for start-up companies, limited funds, so the technical capacity of the permit, rather than buy expensive services , Might as well adopt low-cost DIY program.

3, flexible architecture: to adapt to changes in client-side, server-side services, to deal with the impact of policy issues and other issues. You can switch between different map services and local services, and you can not disable the service due to policy factors.

4, continue to accumulate: For mobile Internet companies, the accumulation of POI data and map data for the vertical area is also the core competitiveness of the product, so the structure must contribute to the accumulation of relevant data.

a. If the client directly accesses the map service such as google map, the client needs to be upgraded if the map service needs to be adjusted (for example, the google map needs to be switched to other map services and the map display content needs to be adjusted) Server-side agent to complete, you only need to upgrade the server.

b, the server can cache frequently accessed map access requests (such as searching around, latitude and longitude positioning maps, location maps according to the address, etc.) can greatly improve performance

c, the server can increase the number of operations and data on the map service provider's results. For example, the server can aggregate its own POI data and data from other service providers and add it to the google map result set

d, the client is not very suitable for doing some complex calculations, such as POI and other content data aggregation, layer operations, the server to complete more appropriate

Of course, the use of server-side proxy approach also has some problems, such as google map on the number of api calls per day may be limited, using the client ready-made SDK development is relatively simple and so on. Specific needs based on the actual needs of their business using the right architecture.

Source: http://www.yeeach.com