Wednesday, August 8, 2012

Architecture Diagram between User Input, Google API and Google Engine

ARCHITECTURE DIAGRAM


GOOGLE ENGINE <- Call Google API's- GOOGLE API <- USER INPUTGOOGLE ENGINE -JSON Data Results-> GOOGLE API -Site Object-> USER INPUT




When a user inputs something, it is limited specifically to the amount of how many requests a day it is allowed. With the Google API (Google AdWords API – lets developers builds applications that interact directly with the AdWords platform. You can develop it in many popular programming languages such as Java, PHP, Python, .NET, Perl, Ruby, and JavaScript.), if the request surpasses the limited the user will receive an error message. The limits can be reached if you send too many requests a day, sending requests too fast, sending requests too fast for too long or otherwise abusing the web service, and exceeding other usage limits.

When someone is using Google API, the API will call on the Google App Engine (it lets you run web applications on Google’s infrastructure), with it, you can create your very own domain name using the Google Apps.

Google App Engine is written in several languages, this include the JSON or the JavaScript Object Notation. JSON format is sometimes used in serializing and transmitting structured data over a network connection. JSON is also used primarily to transmit data between a server and web application, serving as an alternative to XML.

As the result of the Google Engine that was released by the JSON based Google Engine, you’re Google API (which is made using .PHP) must also synchronize with it.

The Site Object which provides access to properties in the SDF file as well as some useful methods that make it easier to process template files and it is used for that reason.