My only concern would be performance. Althought your service layer would run on the same host(s), you will be accessing them through a web service call (XML over HTTP). I would think that this would be much less efficient than making a local call to a component on the same JVM server. Furthermore, I don't think that you would be able to cache your service layer if it is invoked as a web service.
Perhaps a better approach would be to place your service layer components into a discreet folder and add mappings to that location from your other instances. That way, all server instances can share the same deployment of your service layer.
Anybody else have any thoughts on this?
Damon Gentry
Hi all,
I have an architectural question, which conceptually, sounds good.
Server is Dual Processor, 8GB of memory, 100GB of drive space (part of a cluster of 4 servers).
I want to create the following instances:
Instance1: App1
Instance2: App2
Instance3: Flex
Instance4: Misc. (Schedule Tasks)
Instance5: Service (Model and Data layer for all the above instances)
This way we can have all four instances talk to the same service layer, which will enable us to re-use the same model across the applications. We 'd need to invoke the service layer as a web service. All servers in the cluster will have the same configuration.
Please let me know if that sounds like any plan. I want to get as much feedback as possible before I get into implementing this.
Thanks
IDT - eBusiness Program Manager
Work: 408.284.8239
Cell : 209.275.0482
Fax : 408.284.2766
--
Damon Gentry
[EMAIL PROTECTED] ----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com).
CFCDev is supported by New Atlanta, makers of BlueDragon
http://www.newatlanta.com/products/bluedragon/index.cfm
An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
