Forums

by Stephen Persson >> Thu, 20 Jul 2000 21:04:03 GMT

Morning!

Just after a bit of feedback on what the advantages & disadvantages are with having deployed apps either all within the one system or split into their own seperate systems (I'm meaning apps within seperate schemas).

The main advantage I see in having them all in one system is having one system to maintain instead of >1 - easier for Jade upgrades & maintaining/updating any shared superschemas.
But the disadvantage is licensing - if client has 2 licenses, having them in seperate systems means each app can have 2 concurrent connections, versus 2 connections shared between all your apps.

What about system stability though?
If they are all within the one system and one of the apps dies a painful death, does it affect the other apps (this is apps within different schemas)?
Presumably each seperate schema is OK (assuming they don't share map files) but what about shared BaseSchema classes, where different schemas may have instances within the same map file?

What about performance?
Obviously depends on hardware, but on the same hardware, would the apps perform better in their own seperate system ?
With a lot of apps in the one system do you need to increase caching requirements or anything like that to maintain performance levels? Caching is a client workstation thing though isn't it - but you know what I'm getting at.

Comments...

by Craig Shearer >> Thu, 20 Jul 2000 22:45:43 GMT

Well here's my 2 cents worth...

Morning!

Just after a bit of feedback on what the advantages & disadvantages are with having deployed apps either all within the one system or split into their own seperate systems (I'm meaning apps within seperate schemas).

The main advantage I see in having them all in one system is having one system to maintain instead of >1 - easier for Jade upgrades & maintaining/updating any shared superschemas.
But the disadvantage is licensing - if client has 2 licenses, having them in seperate systems means each app can have 2 concurrent connections, versus 2 connections shared between all your apps.

You should check... I'm not sure that licensing DOES work this way

What about system stability though?
If they are all within the one system and one of the apps dies a painful death, does it affect the other apps (this is apps within different schemas)?

Presumeably you'd be running multi-user - only if the server actually crashed would it bring down both apps. But then, server crashes should be very rare indeed.

Presumably each seperate schema is OK (assuming they don't share map files) but what about shared BaseSchema classes, where different schemas may have instances within the same map file?

This shouldn't be an issue - but I think the real challenge is to design a BaseSchema that can be common among all apps, and that you don't need to make changes to for particular apps.... to me, this is a great goal, but one that is not easily achieved.

What about performance?
Obviously depends on hardware, but on the same hardware, would the apps perform better in their own seperate system ?

Because the server is multi-threaded, in theory there shouldn't be any issues in this regard. (But who knows, perhaps there is some single-threaded code that might represent a bottleneck in some critical situations - but I have no knowledge in this area, so am not qualified to comment). So, in theory there should be no difference, and in fact, you might get economies of scale running multiple apps on one JADE server rather than having multiple JADE servers running.

With a lot of apps in the one system do you need to increase caching requirements or anything like that to maintain performance levels? Caching is a client workstation thing though isn't it - but you know what I'm getting at.

Caching is a NODE thing; the server is also a node, and has its own caches (look in the PersistentDB section of the ini file). I would expect that if you're running lots of apps then you'd have a bigger persistent object cache than if you were running just one app. But then, the whole issue of optimum cache sizing hasn't really been explored with JADE yet, AFAIK.

Comments...

Good luck

Craig.

by JADE Support >> Mon, 31 Jul 2000 0:23:09 GMT

<snip>

But the disadvantage is licensing - if client has 2 licenses, having them in seperate systems means each app can have 2 concurrent connections, versus 2 connections shared between all your apps.

<snip>

Stephen,

To run two systems, each with 2 concurrent connections you should have 2 x 2 CAL licences.

Running both systems on the 1 x 2 CAL licence is in contravention of your licence.

Please contact JADE Business Support for further details.

Thanks,
Brian Johnstone,
JADE Support.