The one comment I would make is that with BEA, you have a certain degree of accountability that you don't have with an open-source product. That can be important in a business environment.
I'm probably starting a religious war by posting this, but to some companies it is frankly more important to have someone that's on the hook for problems that arise (and ultimately someone that is legally liable should it really go bad), and you just don't have that with an open-source project. This may or may not be important in your environment, and to be sure there are plenty of advantages that OSS has over commercial offerings and you need to weigh those against the downside(s). I'm not sure I can really comment in terms of how they compare from a technological standpoint. I can tell you that WebLogic is a very robust platform (having previously had some apps running on it), and one benefit that you might see is that having all the various pieces coming from the same vendor might make it more stable (think BEA vs. Tomcat w/JBoss and Axis all pieced together). This isn't necasserily true, but could be. On the flip side, all that functionality comes at the price of added complexity. Tomcat really is very simple to get going with and to administer and tune, and if it has all the functionality you need, this can be a boon to your work. I do have one app hosted on Tomcat. It's what I would call a low-to-mid-size app load-wise (around 75 concurrent users at any given time, on the order of 5,000 requests per day). Tomcat gives us fantastic performance with that load, so my guess it that it will scale quite a bit further. The other thing to be careful about, since you said you are inheriting this app, is if the programmers did anything that is WL-specific that you'd have to deal with to convert. If there's nothing, the decision is in some ways harder because you can justify Tomcat a little bit easier (on cost if nothing else). If there's ANYTHING that's WL-specific, if I were in your shoes, I'd probably stick with WL, just to try and minimize any problems I might get blamed for. It might be tough to figure out if there's anything that might be a problem or not, so possibly it's better to play it safe. In short, I'm a big fan of Tomcat, I use it exclusively during development and use it in production as well, but since you have an existing app already running on WL, and since it is a business environment, all things considered, I'd tend towards the side of sticking with WL. Especially if your company doesn't have a problem with the price, I think my lean would increase! -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com On Sun, September 19, 2004 7:31 pm, Bj�rn T Johansen said: > I am taking over a project that's running on Weblogic 8.1 SP3 today.. They > are only using > the jsp-container and it is time to renew the support agreement with BEA. > So I was just wondering, is it worth it? Or is Tomcat as good as WL or > maybe better? Does > WL have features that is missing in Tomcat? When the time comes to use > EJB, is JBoss as > good as/better than WL? > > So basically, I would like some advice on why I should/shouldn't continue > with Weblogic? :) > > > > Regards, > > BTJ > -- > ----------------------------------------------------------------------------------------------- > Bj�rn T Johansen > [EMAIL PROTECTED] > > ----------------------------------------------------------------------------------------------- > Someone wrote: > "I understand that if you play a Windows CD backwards you hear strange > Satanic messages" > To which someone replied: > "It's even worse than that; play it forwards and it installs Windows" > ----------------------------------------------------------------------------------------------- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
