Comments on: The Problem with EJBs http://www.fuzzylizard.com/archives/2006/09/18/795/ My thoughts on Agile, Java and Ruby on Rails (mostly) Thu, 20 Nov 2008 16:03:30 +0000 http://wordpress.org/?v=2.6.2 By: fuzzylizard http://www.fuzzylizard.com/archives/2006/09/18/795/#comment-6951 fuzzylizard Sat, 23 Sep 2006 04:22:53 +0000 http://www.fuzzylizard.com/archives/2006/09/18/795/#comment-6951 My initial answer to that question is actually twofold: first, I am not convinced that you can just "simply add another server" and get a true 1x scaling factor (i.e., double the throughput of the application) and second, I am not sure that using a distributed method of scaling is the right method of scaling an application. My second answer to your question is that I am not really sure. I have not worked with EJB applications enough to fully answer your question. Over and over again I keep hearing on the net two things, the first is that most real applications only use the web container and second that scalability is highly overused. I think that if you really do need an application that must service millions of transactions a day with 99.999% availability and must be distributed geographically, then EJBs may be the way to go. If I can find some links to better answers, I will post them because I realize that my answer is definitely lacking in evidence to support my opinions. My initial answer to that question is actually twofold: first, I am not convinced that you can just “simply add another server” and get a true 1x scaling factor (i.e., double the throughput of the application) and second, I am not sure that using a distributed method of scaling is the right method of scaling an application. My second answer to your question is that I am not really sure. I have not worked with EJB applications enough to fully answer your question.

Over and over again I keep hearing on the net two things, the first is that most real applications only use the web container and second that scalability is highly overused.

I think that if you really do need an application that must service millions of transactions a day with 99.999% availability and must be distributed geographically, then EJBs may be the way to go.

If I can find some links to better answers, I will post them because I realize that my answer is definitely lacking in evidence to support my opinions.

]]> By: James J. http://www.fuzzylizard.com/archives/2006/09/18/795/#comment-6949 James J. Sat, 23 Sep 2006 00:53:28 +0000 http://www.fuzzylizard.com/archives/2006/09/18/795/#comment-6949 Well what about scalability. How can you scale applications the way you can with EJB. Because with EJB you simply add another server with your EJB code and you're good to go. How would you do it, the "non-EJB" way? Well what about scalability. How can you scale applications the way you can with EJB. Because with EJB you simply add another server with your EJB code and you’re good to go. How would you do it, the “non-EJB” way?

]]>