I’m at a BCS North London event at Google’s London office, listening to presenters from the AppsBroker consultancy extend my understanding of how Google Apps work. We’ve passed through the background stuff about using cloud apps in general and now getting to the meat. If you’ve wondered, like me, what Google APIs can really do, then this is an as-it-goes posting; watch the space! Any errors in understanding or interpretation are mine, of course.
How to write a Google-extended app …
1 – Appscript; 2 – Gadget APIs; s – Data APIs
Just seeing the down side of everything being online rather than on the device; the demo’s gone down through being unconnected. Notwithstanding that I’m doing this on Google’s guest network,, the demo doc is, it appears, “offline”. Embarrassing, even when the demo’s working on a ChromeBook, which admittedly does reboot nice and quickly!
When it’s come back, we get a quick view of the script code inserted into a Spreadsheet to quickly create a form with follow-on technology such as mail-outs based on the respondent’s input, or sending update notifications when an online document is changed.
2: Data APIs, based on REST rather than SOAP (HTML based, IIRC, but can use other languages eg. Java/script .NET, …). Can for example use Data APIs to push data into a shared spreadsheet in real time from multiple users/locations/sources, but maintaining one version of truth.
Google App Engine and Cloud Storage will have a >99.9% SLA from November. Cloud SQL (see Google Blog last week) is under beta.
— adding to the interest level, we just had a fire evacuation and a quick tour of Eccleston Square with the fire marshals. Now trickling back – at least, most of us. I think some people have decided to duck out.
In the pipeline: Google Big Query: online dataset analysis – data mining/BI application. And something called the Google Periodic Table (there’s an extra column in the Transition Metal section …) which visualises the family of applications and extensions. Prediction, for example, can look at web traffic and draw interesting conclusions. Lots of searches on “sore throat” might signal the start of a flu epidemic.
Abbreviated in response to the disruption: Dalim, chair of the Branch, talking about governance. What changes with the cloud? Some of the controls e.g. for change management; assurance from third parties, and provider management; identity and access management (d0 you still have super users?) and monitoring; evolving technology, complexity and challenges. Dalim offers an app assurance checklist [see BCS NLB website in due course].
Q&A … references to Google’s global infrastructure capability; e.g. guaranteeing at least four copies of data on different continents (that is, replication like Lotus Notes used to do). Regarding data protection issues – Google can’t at present commit to (for example) segregating data into the EU though this is being worked on. The offering currently may not be appropriate for heavily regulated in-country enterprises e.g. some areas of government, finance. Google, though, takes the approach that they are not data owners; they are data holders, and would pass access requests to the data owners. And there are data online about which countries request legal discovery, how often, and when. From the security point of view, just a glimpse of the multiple levels of protection applied to data.
Thinking about a portfolio of services: Google Apps will integrate both on-premise (e.g. with AD) and other cloud services (e.g. a strategic partnership with salesforce.com). And there’s a commitment to back data out if a service relationship is terminated. Cloud, to Google, is short term contractable (e.g. 12 month; or a little as 1 month) – no lock-in.
• Google Apps (follow the links)
• Google App Engine, Cloud Storage and Prediction API are open for business, Official Google Blog, 11 Oct 2011
• BCS North London Branch: Past Events 2011 (you may have to scroll for this event; presentations are not yet posted but are expected)
• AppsBroker consultancy