Google shuns Oracle, joins VMware to offer Java development tools for cloud
Google and VMware have rolled out a host of collaborative enterprise-level Java development tools to help interoperability of applications in the cloud at the SpringOne 2GX development conference.
Google shunned Oracle’s Enterprise Java Beans platform for building and deploying enterprise Java applications but chose VMware’s Spring Java development platform instead.
One of the primary reasons of Google siding with VMware could be Oracle’s lawsuit against Google over the use of Java in its Android’s Dalvik virtual machine.
The collaboration aims to make creation, deployment and monitoring of enterprise applications across various devices and cloud systems efficient.
Vic Gundotra, Google vice president of developer platforms said: “By making deployments of Spring Java applications on Google App Engine using Google Web Toolkit generally available, developers can deploy Java applications in production environments of their choice while leveraging rich web front-end across multiple devices.”
The collaboration will result in the launch of three projects in the next two weeks. The projects include merging the rich application development features of Spring Roo with browser-based app development tools of Google Web Toolkit (GWT) to assist developers to create enterprise apps for desktops and mobiles.
It also integrates Spring Insight, an application performance monitor with Google’s Speed Tracer, a performance analyzer with Chrome, to offer a more comprehensive tool to monitor web application performance in the cloud.
Also the companies will integrate SpringSource Tool Suite version 2.5 and Google Plugin for Eclipse which allows developers to create web-based enterprise applications by allowing access to tools used for desktop and server applications, thus enriching Google App Engine APIs.
The major difference between Enterprise Java Beans (EJB) and Spring framework is that EJB is open standard and is designed for vendor independence while Spring is a non-standard technology. Also, Spring apps are locked into Spring itself and to the specific services one chooses to integrate in Spring.
Also Spring framework sits above the application servers and service libraries unlike EJB which is well integrated with app server and service libraries. Thus it is cumbersome to make interaction between the service and the grid while EJB can optimize on the underlying servers and service libraries more effectively.
Since the Spring’s service integration code is exposed via APIs developers can assemble services as needed while EJB allows a predefined set of services, thus limiting flexibility.
| [Source] Software Outsourcing Blog Section: http://www.techomechina.com |
Processing your request, Please wait....
