People should evaluate their architectural needs. EJBs offer a lot of
advantages, but also a lot of overhead, and not necessarily the portability
that one would want, under the current standards and implementations.
If you're not selling CDs over the web, you might not need the horsepower
offered by EJBs. Java beans can offer a lot of the functionality offered
by EJBs, albeit less robustly. You might be able to get by with an
architecture consisting of Java Server Pages, Servlets, and Java Beans,
which would also let you buy a lower-end application server, that has a
smaller footprint and is easier to maintain than the 'enterprise'
models. If you eventually need EJBs, you can always add them on the back
end without disrupting your application design (JSP<->Java Bean becomes
JSP<->Java Bean<->EJB).
-- Curt Springer, Team ND
At 01:01 PM 11/2/99 -0800, Joel Parker Henderson wrote:
> > Two years sounds good. What about the future?
>
>Beyond two years, Sun is moving towards J2EE.
>So are all other major app server vendors,
>except for Microsoft of course which is
>still pitching Windows 2000 and MTS.
>
> > What about incremental costs for procuring iPlanet
> > server? First of all is it a incremental procurement
> > cost or do I have to buy it new?
>
>Pricing hasn't been set yet-- typically we have set prices
>when the feature list is complete and the product has been
>through review by beta customers, analysts, and the press.
>
> > Does sun has a roadmap for ND folks and KIVA folks to
> > embrace iPlanet?
>
>Yes, absolutely. The broad roadap is easy:
>
>Kiva3 --> NAS4 --> NAS4 with EJB --> iPlanet App Server 6
>ND3 --> ND4 --> ND5 with EJB --> iPlanet App Server 6
>
>The migration guides that I discussed before will have specifics,
>examples, tools, and all the rest of the information that you need.
>
> > I don't know how many CIOs lost their jobs because of going the ND way.
>
>That seems odd to write. The answer happens to be zero.
>
>I know that there are a lot of questions going forward.
>There will be plenty of time to get these questions
>answered in the kind of detail that you want and need.
>
>ND5 is (and will continue to be) an exceptionally powerful platform for
>running your web applications. According to all press reviews, ND5 is the
>most powerful and scalable cross-platform app server, and I expect this
>will be true until iPlanet App Server 6 debuts next year.
>
>The only difference is that new customers will buy IAS6 instead of ND5,
>and that your new projects can take advantage of the open EJB standard.
>
>Migrating to EJB is something that everyone who uses any app server
>will likely want to do sometime in the next year or two, because EJB
>will improve key deployment issues like portability and scalability.
>
>I want to emphasize that the major migration hurdle will *not* be from
>ND5 to IAS6, but rather from ND5+CSp to ND5+EJB. When you have your
>projects migrated to EJB, it will be quite easy to move them to IAS6,
>or to WebLogic, or to any other EJB/J2EE application server you want.
>
>So your CIO can do three things to keep his job:
>
>1. Realize that ND5 will be around for quite a while,
> and that all of his investment is fully protected.
> If he needs official statements, contact Bill Lazar
> by sending email to [EMAIL PROTECTED]
>
>2. For new projects, encourage his developers to
> use ND5 with EJB, which they can do right now.
> For existing projects, have a two-year plan to
> migrate them from ND3 to ND4 to ND5 with EJB.
>
>3. When IAS6 is ready next year, have his developers
> evaluate it and compare it to other EJB appservers
> like those from BEA and IBM; choose the best one.
> All his ND5+EJB projects will be in good shape
> and ready to move easily to the best EJB server.
>
>
>Cheers,
>
>Joel
_________________________________________________________________________
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
