|
> Why do you think all the overhead of EJB > will somehow translate to scalability? It's more a question of the scalability of distributed components vs. the scalability of efficient interfaces. In one case, more CPUs can be added to the farm, in the other case, applications themselves use less CPU time. An architecture that used say 1/10 the amount of CPU time while running on one (1) CPU would be more scalable than an architecture where components could be distributed across ten (10) CPUs. The dilemma for developers is that broadening the scope of Java applications will ultimately lead to a requirement for distributed components. J2EE is a distributed architecture, and must be so, simply because any broadly scoped 100% Java application, separating user interface, business logic, control logic, and database I/O into separate components, will be a comparatively CPU intensive proposition. Nathan.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
