Thursday
Sep062007
Why doesn't anyone use j2ee?
Thursday, September 6, 2007 at 1:59AM
From a reader:
eBay uses Java, but in a very pragmatic way. They use servlets, an application server, the JDK, and they do the rest themselves. They skip JSP, entity beans, and JMS.
When you need to scale putting all your eggs in one basket is a risky strategy. Why use JSP when you can do better? When use entity beans when you can do better? Use servlets because they are a very effective way of handling http requests. Use Java because it is fast, runs everywhere, and has a boat load of libraries you can use to build your build your custom system.
Probably the major reason J2EE is absentee is simply LAMP. LAMP is just so incredibly functional for most 2-tier shared nothing sites they don't need a better infrastructure for writing an application tier.
Personally, I pretty excited about GWT which uses Java and servlets. We'll see if that starts to take off a little bit more.
> Was reading through your very interesting/useful site.
>Most of the architectures are non j2ee-Does that mean that
>there aren't enough websites that are scalable(with youtube
> like userbase) built with j2ee tech-would like to know if there
> are any and their architecture as
>well.
eBay uses Java, but in a very pragmatic way. They use servlets, an application server, the JDK, and they do the rest themselves. They skip JSP, entity beans, and JMS.
When you need to scale putting all your eggs in one basket is a risky strategy. Why use JSP when you can do better? When use entity beans when you can do better? Use servlets because they are a very effective way of handling http requests. Use Java because it is fast, runs everywhere, and has a boat load of libraries you can use to build your build your custom system.
Probably the major reason J2EE is absentee is simply LAMP. LAMP is just so incredibly functional for most 2-tier shared nothing sites they don't need a better infrastructure for writing an application tier.
Personally, I pretty excited about GWT which uses Java and servlets. We'll see if that starts to take off a little bit more.
Reader Comments (3)
Keep in mind that this site focuses on high scalability presentation/website technology and architecture.
Rest assured that J2EE is present on the backend, especially if asynchronous processing is required. You don't see a lot of php for backend systems in financial, telecommunications or logistics verticals. MQ Series and Tuxedo are two of the high performers and have a dedicated, an relatively quite, following.
"Why doesn't anyone use j2ee?
" - you mean there are people/business that don't use j2ee? Wow... I sure don't know of many :)
I think they are referring to why websites with the most traffic don't run J2EE. Have you ever been to a website that runs using J2EE? You can tell within the first 10 seconds after you still haven't gotten any page back. Most Java sites, usually bank sites, are slow as hell. Java folks can argue all they want about how fast Java is, but it is definitely not the case in the web world. There's not a top 50 website that runs pure J2EE.