Java201.com

• Improve availability in Java enterprise applications by Ajay Raina, John Jimenez, Govind Nishar, Ning Yan   - [Clicks: 32]
  In today's 24-7 world, high-availability is an important requirement for any Web application. Specially designed infrastructures can help increase the availability of Web applications, but infrastructures by themselves do not make applications highly available. This article focuses on the design of high availability applications. The authors discuss best practices drawn from their work in designing JEE (Java Enterprise Edition) applications that maintain 100 percent availability.
  http://www.javaworld.com/javaworld/jw-12-2005/jw-1226-jee.html - Dec, 2005
• Six Steps to Faster J2EE Apps: Performance Tuning with JSP and Servlets by Sridhar M S   - [Clicks: 60]
  Can your J2EE application sustain a large number of client requests simultaneously? Or does it become sluggish, with painfully slow response times? There are many reasons for such performance bottlenecks and many ways to prevent them. However, sometimes it's just a matter of following some simple best practices that can make all the difference. The following are six simple changes you can make, some in the design and some in the coding phases, that can help you build faster, more robust applications.
  http://javaboutique.internet.com/tutorials/tuning/ - Dec, 2005
• J2EE project execution: Some best practices by ShriKant Vashishtha   - [Clicks: 56]
  Software development is difficult. We may talk a lot about design issues, related solutions, and patterns, but project execution in itself is an area where many patterns and best practices are needed to save invaluable time. This article presents three such practices for resolving day-to-day software project execution problems.
  http://www.javaworld.com/javaworld/jw-11-2005/jw-1114-j2ee.html - Nov, 2005
• Secrets of lightweight development success, Part 3: The emergence of Spring by Bruce Tate   - [Clicks: 87]
  Lightweight containers provide a means for organizing the glue code for an application. The Spring framework is the predominant lightweight container. Spring contains a lightweight container, an aspect-oriented programming framework, and glue code that makes it easy to integrate hundreds of open source frameworks.
  http://www-128.ibm.com/developerworks/opensource/library/os-lightweight3/ - Jun, 2005
• Secrets of lightweight development success, Part 2: How to lighten up your containers by Bruce Tate   - [Clicks: 67]
  Businesses need the enterprise services that heavyweight architectures, such as Enterprise JavaBeans (EJB) technology, provide, but such architectures can be overkill for everyday problems. This article introduces lightweight containers and explains how they can provide the services your business needs without tying you to a given programming model.
  http://www-128.ibm.com/developerworks/java/library/os-lightweight2/index.html - Jun, 2005
• Secrets of lightweight development success, Part 1: Core principles and philosophies by Bruce Tate   - [Clicks: 81]
  Lightweight development is a huge topic, and developers throw the term around so often that it's hard to tell what it means. This first article in a series on lightweight development introduces you to the core principles and philosophies behind the movement.
  http://www-128.ibm.com/developerworks/opensource/library/os-lightweight1/ - May, 2005
• Maximize J2EE and database interoperability for performance by Robert Maness   - [Clicks: 44]
  Most application performance management (APM) solutions target and analyze the performance issues of only a single tier in a J2EE application. This approach is not enough for solving the performance problems of complex architectures. The right APM tool should let you drill down from the J2EE tier into the database tier to ensure performance issues are quickly resolved.
  http://www.javaworld.com/javaworld/jw-02-2005/jw-0228-apm.html - Feb, 2005
• Software Infrastructure Bottlenecks in J2EE by Deepak Goel   - [Clicks: 57]
  Scalability is one of the most important non-functional requirements of a system. But there could be several bottlenecks within a system, which might prevent it from being scalable. In this article, we try to analyze the case in which the software infrastructure becomes a bottleneck, long before any of the hardware resources (such as CPU, memory, disk space, and network speed) are fully consumed. This is a tricky problem whose solution is explored below.
  http://www.onjava.com/pub/a/onjava/2005/01/19/j2ee-bottlenecks.html - Jan, 2005

[Top]

• J2EE Best Practices by Darren Broemmer   - [Clicks: 31]
  Darren Broemmer, author of "J2EE Best Practices" and senior software engineer for Freddie Mac, talks about architectural style, where messaging and EJB fit into an architecture, and a few other issues such as performance, service versioning, and more.
  http://www.theserverside.com/talks/library.tss#broemmer - May, 2005

[Top]