-----Forwarded Message----- From: Leo Simons <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: newbie looking for orientation Date: 18 Nov 2002 13:20:12 +0100
On Mon, 2002-11-18 at 12:33, Joerg Buchberger wrote: > Hi. Hi Joerg! > I've got a couple of questions on Avalon and Phoenix: no prob; keep 'em coming! > 1. How stable is Phoenix? rock-solid. It can run for 2 years without crashing, memory leaks or performance degradation. > 2. Is Phoenix to be replaced by another Avalon project now > or in the near future? (As I don't really get yet how ECM, > Fortress, Merlin, Excalibur + Phoenix relate to each other > and where they are going - where is Avalon heading?) no, it won't be replaced. Yes, there might be future alternatives for some use cases. ECM is something lightweight, something you can easily embed in a servlet engine (this is how cocoon works), Fortress is basically an unstable next-gen ECM. Merlin is somewhere in the middle between fortress and phoenix and also unstable. We are not so sure which way we are heading just yet. > 3. Is there some component or function, which allows > Phoenix to supervise the status of its blocks? no. > Can Phoenix > thus (be made to) restart a block when necessary? yes. There is a JMX management interface through which you can do things like this. > 4. Does Phoenix offer its Blocks any means to communicate > centrally? no (this is by design; recommendation is to use an RMI-like mechanism or JNDI). Note that blocks _in the same server application_ can get access through each other through something called a ServiceManager. > 5. Is there anyone running a Phoenix based system > professionally, i.e. commercially? yes. Multiple big companies with big deployments. Unfortunately, no-one in the know is allowed to be more specific on that. > 6. How about maintainability and testability of Phoenix > running several servers as blocks when operating system > changes, JRE changes, server-app changes come into play? Do > you think this is manageable? Any experiences someone? it is workable. Phoenix runs on jdk 1.3+, requiring (obviously) a solid implementation for io and threading. You can deploy a .sar application to windows, linux and solaris with no problems. The same is true for phoenix. > 7. How many of the 15(?) people contributing to Avalon are > working on Phoenix? You can see quite a few people working on phoenix by looking at the mailing list archives for phoenix-dev. I also suspect that some people that work on it are liaisons for bigger company development teams. Adding people like me (who don't do a lot of coding anymore but do provide phoenix 'user support'), I'd estimate about 10 people currently. > 8. Are there any public reviews or others opinions on > Avalon availabe somewhere since it is also contributed to > JSR111 Java Services Framework? there was an article on javaworld some time ago, there's some people who go wild about it in their blogs, but no analysis by gartner, no showcase of if on the sun site, or anything like that (that I know of). best regards, - Leo Simons -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
