By taranfx
via taranfx.com
Published: Nov 28 2009 / 09:11
![]() | |
| BIRT 3.7 | |
| Written by: Michael Williams | |
| Featured Refcardz: Top Refcardz: | |
| 150+ Refcardz Available · Get them all | |
By taranfx
via taranfx.com
Published: Nov 28 2009 / 09:11
Comments
ceaseoleo replied ago:
As most of the comments from the article have stated, I think azure is more fairly compared to EC2, or rackhost rather than app engine. App engine is very unique in that its not like a vps. Also the guy must not be a java developer because to think that not running EJB is a bad thing is ridiculous. I think most people using JPA, and spring/Seam as glue code,with some front end is enough.
superboy replied ago:
>> Also the guy must not be a java developer because to think that not running EJB is a bad thing is ridiculous. I think most people using JPA, and spring/Seam as glue code,with some front end is enough.
Uhmmm, FYI 50-60% of Enterprise applications in PROD use EJBs. Only newer apps have trend shifted to use of Spring/POJO.
ceaseoleo replied ago:
well won't you be building newer apps if you are going to use google app engine.. not sure how familiar you with it, but you more than likely won't be able to do a straight migration with the restrictions on the jvm.
AllureFX replied ago:
@superboy I don't follow your reasoning/implication: the article compares Azure and GAE, and Azure doesn't support EJB either, right? What's your opinion on Azure vs. GAE specifically?
regis.decamps.info replied ago:
GAE does not support EJB, but it's nothing compared to the severes restrictions to the classpath.
regis.decamps.info replied ago:
I think a comparison of the hosting "in the cloud" must include Amazon EC2. After all, there are the first.
Voters For This Link (9)
Voters Against This Link (5)