| |
|
WebLogic 9.0 takes J2EE to a new level of reliability and scalability |
|
|
|
Written by Content Team
|
|
May 29, 2005 at 06:56 PM |
|
Page 4 of 7
IndicThreads >> The BEA site says that "WebLogic Server 9.0 is the most significant BEA application server release to date." That's quite a claim considering BEA's track record.
Jesper Joergensen >> *Laughing*. We are always extremely proud of the achievements we make in our latest release. We realize that we have a very strong record regarding BEA WebLogic Server releases, but we still feel that this release will be very significant. While some people thing that app servers are ?just a commodity? or ?all the same?, we see a tremendous opportunity to make Java and J2EE available in a world that requires ?zero downtime?.
"We see a tremendous opportunity to make Java and J2EE available
in a world that requires zero downtime..."
Until now, Java and J2EE have only been used for medium range critical systems. Super reliable systems such as telco switches are more hardware based or they are based on older and less flexible but more reliable software systems.
WebLogic Server has now reached a level of reliability and scalability that allows it to replace some of these super reliable systems. This enables our customers to build new services in a much more rapid fashion using more common J2EE skill sets.
"WebLogic Server has now reached a level of reliability and scalability
that allows it to replace some of these super reliable systems...."
That is truly significant.
IndicThreads >> Open source software is all over Java and now even the application server space has several good open source alternatives. So what's BEA's answer if a potential customer says "Why should I not just use an open source servers instead of paying you hundreds of dollars for the WebLogic server?"
Jesper Joergensen >> When you compare application servers, you are just comparing J2EE implementations and if all you need is a J2EE implementation then you can probably use an open source application server. But BEA?s customers need much more than that. The J2EE implementation is just the ?surface? of an application server.
"If all you need is a J2EE implementation
then you can probably use an open source application server..."
Once you start a J2EE development project, the application server you use will determine how fast you can do your edit-compile-debug cycle. It will determine how easy it is to move you J2EE application from development to staging to production. Once you need to deploy, operate and maintain your J2EE application, your J2EE application server plays an even bigger role. It determines how easy it is to update the application, how easy it is to scale up and down (if possible at all), and it determines how much visibility you have into the operation of your application.
All of these things add up to much more than the cost of just writing the code. In fact, the costs of maintaining application lifecycle and of managing a runtime environment easily dwarves the costs of the software you are using.
"In fact, the costs of maintaining application lifecycle
 and of managing a runtime environment
easily dwarves the costs of the software..."
Â
But of course these requirements vary from project to project and you should always make sure that you understand what your requirements are and what infrastructure you need for a particular project so that you can make cost-efficient decisions.
|
|
|
|
Home | 
