
As it stands, google runs my favourite search engine, my favourite web browser, this blog, my email and even my calendar. They also help me get from A to B, watch videos that I'm interested in and find the cheapest price for things that I want to be.
Since I do all of this whilst logged in to my google account - it stands to reason that google owns a worrying amount of information about me. Sometimes I worry about it, but then I stop worrying, because, after all, I can stop using google's services any time I like, and, to be fair, my habits as an individual probably aren't that interesting to a large, multinational organisation like google.
Google application engine, on the other hand, completely changes the name of the game.
GAE (the application engine) is a service provided by google that allows online web applications to be built using Python and then hosted - completely free - on google's servers. They promise that the engine is extremely scaleable - that means that an application created using GAE could be used by 4 people, or by 4 million people. The service could be used to create almost ANY type of data processing system, provided that it is web oriented.
That sounds wonderful, but it raises the question of ethics. Google operates in hundreds of different legal climates, although it is in itself an American organisation. What happens when the application engine is used, for example, to store information about the mis-treatment of prisoners in one country, or measures taken to drive out dissidence in another. On a less ethical note, is it really a good idea to trust the innermost aspects of the workings of your organisation to another company? No less one that is incredibly good at indexing and data mining.
In fact, I believe that the British Data Protection Act makes it illegal for any company to pass your data to another organisation without seeking permission from you for it first. If google ran servers in countries that DON'T have similar data protection laws, you would need to ensure that none of your customer's information lands on those servers - that's another requirement of the Data Protection Act.
Nevertheless, Google's application engine is a very useful and interesting peice of technology. It is easy to work with, includes a set of tools that are fairly standard for web applicatioons in Python, and encourages best practises for scaleability by providing an excellent set of standard tools. It includes a powerful data storage system (with its own problems, mind you - I might discuss those in another post), and it can run easily in both development and production environments.
Using google's servers can be extremely useful if you run a small to medium sized site and you don't mind passing your data to google. In fact, you can run the engine on a server of your choosing, as long as it supports a django environment. That was your information is NOT all passed to google - useful when you start storing information that matters.
All in all, I believe that GAE is a fun bit of technology. It could be used in a fairly large number of situations to make life easier and simpler for the amateur web application developer. Should it be used for larger organisations? Probably not - or at least, I believe it shouldn't.
Bye for now!