|Given my relative lack of experience with these issues, I was wondering if
|any of you with more experience would care to comment on these scenarios.
|Are there alternatives I have not presented here which could afford us the
|advantages of running the appserver on a separate box without the cost of
|RMI serialization? Is the cost of RMI serialization high enough to justify
|pushing jBoss onto the webserver box, essentially collapsing a 3 tier
|architecture into a two-tier one?
be careful when you say "RMI serialization" it is really "serialization" in
other words, even the JDBC serialization is to be factored in.
That being said, yes, in my mind the "network" layer for EJB is a lot of
boloney from the client server days. The honest truth is that the J2EE
stacks will live like pancakes one on top of the other and embedded in more
global frameworks (a web server, a development tool, a j2ee third party app)
etc etc.
YOU NEVER SEE THE FREAKING NETWORK
Collapsing stacks is good, teh way to scale is to multiply the stacks :)))
the DB should be unified behind and that should be the only "network
serialization".
OH MY GOD WE JUST REDISCOVERED SAP :0)!!
We need to address some clustering issues soon, there are some tremendous
ideas on how to speed things way way up even with the DB!!!! stay tuned
marc
|
|Sincerest regards,
|Chris Todd
|
|
|
|--
|--------------------------------------------------------------
|To subscribe: [EMAIL PROTECTED]
|To unsubscribe: [EMAIL PROTECTED]
|Problems?: [EMAIL PROTECTED]
|
|
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
