Client/Server Architecture on the Mobile Platform {1}

by Eric C
When it comes to creating mobile apps for smartphones, such as for Apple iOS or for Google’s Android, such apps need to be created based on the client/server architecture. Many of today’s apps require the use of internet or cellular data to access information requested by the users. Each command or query initiated by the user is then sent back to a web server, then to a database for processing, and finally the information is sent to the user. In an article written by Anthony Kosner from Forbes, he talks about how the speed of Siri and Google’s Voice Search relies on the client/server architecture. Apparently both Siri and Google’s Voice Search relies on a server architecture to send data back for processing. The way Siri works is by saving the spoken command to a compressed audio file and is sent to Apple’s servers for processing. From there, Apple’s servers do the major processing and the results are then sent back to the user a compressed zlib binary plist (simply a binary/text file). Google’s Voice Search uses a similar method as well. Since the requests are processed on the server, it is important for database designers to efficiency design the server and database to handle a plethora of requests. Not only does the performance is affected by the server, so is the type of cellular connections used on smartphones. As a result, the client/server architecture is a very important consideration when designing web-based databases. Speed and efficiency are what customers look for and if it’s not there, several competitor apps are available. read more...