Google’s App Engine: getting serious about the enterprise market
Other considerations range from its beta status (could change without warning, pricing may shift without much notice, somewhat limited functionality such as read-only services) to partial support of the Java programming language. Perhaps the major consideration is the one-way nature of the Google App Engine. Software built for the App Engine cannot be easily repurposed to run on a competitive system. One Google reseller pointed out, "Google Apps has a Hotel California aspect." An accurate observation.
More significant are built-in limitations to the system. For example, certain operations are not permitted. You have to upload data to Google in chunks of 10 megabytes per file transfer. Another consideration is that Google has been criticized for limitations in its enterprise security support. App Engine includes additional security functions. A useful thread appears on Google Groups (http://groups.google.com/group/google-appengine/browse_thread/thread/36a262be410327a6/2bcc2d92fd1ca7ab?lnk=raot).
Oracle has few reservations about Google, its enhanced App Engine or the Secure Data Connector. The company has announced plans to develop solutions for the sprawling Oracle database customer lineup. TechTarget, a trade news publication, pointed out that Oracle will use Google to add Google-type features to customer relationship applications. Oracle senses cost advantages, technical benefits and the odor of a sizzling steak in its Google tie-up. The meshing of Oracle and Google technology makes sense. As new workers coin organizations, the request "I want a Google service" is becoming increasingly important.
There are some dissenters, particularly about Google’s support for Java, an enterprise programming language. Sun Microsystems has expressed some concern that Google is not supporting the full range of Java functions. Google, on the other hand, is supporting Java functions that hit the sweet spot for enterprise developers. Google’s engineering makes it comfortable for a Java developer to hook into the Google resources. The jury is still out, but Google’s clout is considerable. Sun Microsystems is mired in a financial swamp. Oracle’s plan to acquire Sun, which is expected to close this summer, adds another unknown to the swirling mix of technologies used by Google and Oracle. Is Google redefining Java to meet its own goals? That’s a good question, but one that cannot be answered at this time.
How important is the Google App Engine to Google’s enterprise ambitions? In my opinion, it is very important for three reasons.
First, it shows explicitly that Google’s engineers can make the Google services available to an enterprise via network connections. If the market responds, the computing approach will be to use Google for heavy lifting and local computers to process certain data. The payoff will be lower costs and a way around the brutal on-site information technology burden that weighs upon many organizations.
Second, the customer remains in control of his or her information. The claim that Google does not support secure data access is no longer accurate. No system is foolproof, but Google has made significant security strides. Oracle, for example, is no weak sister in the enterprise, and the company is grabbing the App Engine controls and driving forward.
Third, the App Engine enhancement makes clear that Google will complement the Google Search Appliance, Google Maps and the OneBox API with an enabling layer of middleware. The technical improvements to App Engine leave no doubt that Google wants to get a larger share of the enterprise market’s investments in software and systems.
Is the App Engine for you? In my opinion, if not today, soon, very soon. The bait is "free" and looks quite tasty.