|
Sponsored Links
Resources
Enterprise Java Research Library
Get Java white papers, product information, case studies and webcasts
|
News
News
News
|
Messages: 15
Messages: 15
Messages: 15
Printer friendly
Printer friendly
Printer friendly
Post reply
Post reply
Post reply
XML
XML
XML
|
 |
Google's App Engine or Amazon's Elastic Computing Cloud
Google has announced a Google App Engine which allows you to run your own applications on Google's infrastructure. It's a different approach from Amazon's EC2 which allows you to host your own virtual machines on their infrastructure. However, they are close enough to be competing.
EC2 gives you your own VM allowing you to run about anything you'd like and then throws on top several additional services like Amazon Simple Storage Service, Simple DB, and Simple Queue Service service. App Engine allows you to deploy Python applications on Google's infrastructure, with other languages coming. It also offers a DB service as well as several other services (user management and mail, for example).
Both have the promise of massive infrastructure on demand. App Engine provides it automatically while EC2 requires some tooling. In either case to truly take advantage of the service it seems you'll end up with - if not vendor lock in - a high barrier to moving to another vendor. Both are very interesting offerings and offer great solutions to scaling fast even as a small company. Which approach appeals the most to you (assuming Google will soon support your favorite language)? [Editor's note: who says Python isn't one's favorite language? Oh wait - I forgot some whitespace...]
|
|
Message #250215
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
 |
Exciting times...
These are both very exciting services and I think they will both create a major and profound change in the application development market because application deployment and administration is yet another barrier for any starting business.
Looking at what Google has to offer here, I see a lot of stuff: you can develop an application, deploy on the Google cloud and consume many Google services as widgets, embed search capabilities, access to videos and forums and all of that is native to your application. Not only storage, but real applications.
Couple of questions and thoughts about the issue:
- What other business models will Google create from this service in addition to hosting/transaction/storage/bandwidth business models? Will they utilize the information created from people surfing to several applications hosted by them? Provide cross-site data about the users to site owners?
- Is Google planning to offer a hosted development environment to complement their offering?
- GWT support sometimes in the near future?
- Are some sort of web-services (not only HTTP get query strings) supported? this would open up a zillion possibilities.
- Any mash up API layer planned soon by these two giants?
|
|
Message #250230
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
 |
GWT is already supported
It already supports HTML and JS, so technically GWT is supported. You can write your server-side in Py and you got an end-to-end AJAX web app story
|
|
Message #250231
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
 |
Re: Vendor lock in
In either case to truly take advantage of the service it seems you'll end up with - if not vendor lock in - a high barrier to moving to another vendor.
I smell a new standard coming... maybe JSR <xyz> Web App Hosting Specification? ;-)
|
|
Message #250237
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
 |
A totallly different beast
I have been looking at all the fuzz Google App Engine has created, but no matter how hard I try, I cannot see it as a serious competitor of EC2 (at least not yet).
Amazon EC2, although it requires some tooling and image configuration, gives you full freedom. Many shops are using it for all sorts of deployments, from standard websites to complex grid infrastructures. For example, many of our customers are able to deploy GridGain (open source Java grid computing product) on EC2 with minimal effort. We are currently also working on migrating our own distributed JUnits from dedicated data center to on-demand EC2 cloud.
Google App Engine, on the other hand, targets a totally different market. The choice of supporting only Python and limiting external connections to HTTP(S) says to me that they only care about WebSite deployments at this point. It is a Python Web Hosting data center. You simply don't have the same flexibility here as with EC2, but if you are a Python website, then this could potentially become an ideal choice for you.
But hang on a second... After all we could always rewrite our product in Python ;-)
Best, Dmitriy Setrakyan GridGain - Grid Computing Made Simple
|
|
Message #250238
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
 |
Re: A totallly different beast
Funny but it seems that GAE could have been easily created on top of Amazon EC2. In fact, GAE is nothing more than a good shared Python hosting (no threads, no local drive access, etc.) – perfect application to run on Amazon EC2.
As Dmitriy mentioned – these are two very different things.
Best, Nikita Ivanov. GridGain – Grid Computing Made Simple
|
|
Message #250240
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
 |
Only Py?
Hey, you guys, Don't you think it is obvious that other development stacks will get the same support?
Ok, it's not the most flexible platform, it's focused on the web while EC practically does everything, but the generic principle is the same and obviously a competition in this segment.
Y.
|
|
Message #250248
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
 |
Re: Google's App Engine or Amazon's Elastic Computing Cloud
Google has announced a Google App Engine Ok, now the problem is that I _need_ an account. The 10000 user initial limit has already been reached but I just cannot live without it anymore.
Help, please, An addicted google maniac
|
|
Message #250259
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
 |
SimpleDB Service
Only quibble with this service so far is that it isn't true REST. It is simply GET-based RPC. Call me a purist but I think it is bad mojo to have all your PUT, DELETE, UPDATE, actions be GETS. Too much like having the "car blow up now" button next to horn on the steering wheel. Or, to be less cheeky, GETs should not have side-effects.
|
|
Message #250283
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
 |
Re: Exciting times...
Java sucks It's hard to argue with that, especially with all the really strong supporting evidence you've provided. Keep up the good work!
|
|
 |
New content on TheServerSide.comNew content on TheServerSide.comNew content on TheServerSide.com |
 |
 |
Reza Rahman continues to explore the features of the proposed JSR 299, Contexts and Dependency Injection for Java EE (CDI). When approved, it promises to be a key feature of Java EE 6.
(January 21, Article)
Ted Neward is an independent consultant specializing in high-scale enterprise systems, and an authority in Java and .NET technologies. He is the author and co-author of several books, including Effective Enterprise Java. At TheServerSide Java Symposium in March, he will be presenting sessions on pragmatic architecture, ECMAScript and Scala.
(January 15, Article)
Now that Oracle is absorbing Sun Microsystems, there mixed views on what should come of the Java Community Process (JCP). While some say Oracle should become the new steward of Java and keep the JCP much as it was, others argue that it may be time to open-source this widespread language.
(November 24, Article)
Reza Rahman explores the features of the proposed JSR 299, Contexts and Dependency Injection for Java EE (CDI). When approved, it promises to be a key feature of Java EE 6.
(November 2, Article)
SAML is an XML-based standard for exchanging authentication and authorization data between security domains. The single most important problem that SAML was created to solve is the Web browser Single Sign-On problem. Many organizations are debating whether to stay with version 1.1 or move to 2.0. This article makes observations about both options.
(September 28, Article)
Joe Ottinger takes a look at how people learn, and applies it to the practice of programming. He notes that understanding how people learn is an essential part of working in a programming team.
(September 22, Article)
Stephen Maryka gave us an article about the Asynchronous Web and posed a number of questions that get examined like an approach to delivering Asynchronous Web capabilities through extensions to existing Java EE technologies.
(July 14, Article)
JavaServer Faces Flex goal is to provide users capability in creating standard Flex components, part of flexSDK which is open sourced through MPL license, as normal JSF components. This article by Ji Hoon Kim will provide an overview of creating a simple multilingual JSF page consisting of JSF Flex tags.
(June 29, Article)
In this session Jeff explores the key characteristics of successful SOA projects. He covers some of the patterns, and anti-patterns, tool sets, and strategies that he himself learned the hard way. Last, he provides a strategy and blueprint for achieving a high likelihood of success in your SOA project.
(June 23, Tech Talk)
Ari Zilka, CTO of Terracotta, Inc., talks about the new features in Terracotta 3.1, announced during JavaOne and available now.
(June 15, Tech Talk)
In this Tech Talk, Josh Long explores an integration challenge using Spring Integration and walks through the implementation, employing and expanding on the basic patterns of Enterprise Application Integration to tie together components into a function integration solution, and then demonstrates how Spring Integration helps address the integration requirements.
(June 15, Tech Talk)
In this Tech Talk, David Geary teaches you: The basics of Google Web Toolkit; How to implement Ajax-enabled applications in Java; Internationalization; Hooking into the browser history mechanism; Remote procedure calls.
(June 4, Tech Talk)
Jon Kern discusses the best architecture/technical solutions and ensure that they are repeated by all developers. By tackling the architecture up-front in a serial manner, subsequent parallel development will be much more manageable and predictable.
(May 28, Tech Talk)
This keynote describes the frustrations of modern knowledge workers in their quest to actually get some work done, and solutions for how to guard yourself against all those distractions. Neal Ford talks about environments, coding, acceleration, automation, and avoiding repetition as ways to defeat the misguided attempts to sap your ability to produce good work.
(May 26, Tech Talk)
Gil demonstrates how new, aggressive uses of already abundant compute capacity by common applications offer competitive value for application designers.
(May 21, Tech Talk)
Chris Keene introduces WaveMaker as a new way to automate the ability to generate Hibernate classes in order to more quickly bring OR mapping into an application.
(May 19, Article)
Mastering EJB was one of the original and most influential EJB books in the industry. Mastering EJB III now returns with two new expert co-authors, updated for EJB 2.1 and 30% new chapters including security, integration, best practices, open source, and more.
(Book PDF Download)
The Application Server Matrix is a detailed listing of J2EE vendors and their application server products, with information on latest version numbers, J2EE spec support and licensing, pricing, platform support, and links to product downloads and reviews.
(Application Server Comparison Matrix)
|
|