[Openroad-users] AppServer State Recovery

[Fabian Anderson]

Hi All,

            I am looking for any ideas or comments on three basic
approaches to state recovery on a shared application server using
ASOLib.

 

            First some background might help.  The State persistence
features of ASOLib seem to be a little less reliable than I had hoped,
so a state recovery mechanism is being considered for robustness.
Second, the shared server is being used for scalability and with this in
mind, we can not be sure that the same app server will be used from one
call to another.  The objects requiring state persistence are quite
large, complex and difficult to serialise (although not impossible).

 

            The three basic approaches are passing state between
client/server, serialising objects and saving state to database, a state
machine with command pattern.

 

1)       passing state between client/server.  This seems like a lot of
network IO required just in case the state becomes lost by ASOLib and
uc_bus_pol_mgr.

2)       serialising and saving state also seems like a lot of database
IO just in case the state becomes lost

3)       a command pattern state machine passes a command list between
client/server and executes the list if the state becomes lost. (seems
more scalable).

 

 

NB:  Option 3 would probably offer the lowest performance if the state
needed to be recovered on every app server call, but it is expected that
about 5% of app server calls will need to recover state information, so
I think implementing a command pattern inside a state machine would be
the best option for overall performance.

 

Any thoughts, comments, common pitfalls or other approaches would be
greatly appreciated.

 

Thanks,

Fabian Anderson

Systems Analyst / Programmer

Fintechnix Pty Ltd

 

 

 

            

 

 

 

 


Specialist providers of back and front office systems for the financial services industry.
Featuring:  Fintechnix(r)
Disclaimer: 
Notice: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it.
Any views expressed in this message are those of the individual sender,except where the sender specifically states them to be the views of Fintechnix Pty Ltd.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://peerlessit.com/pipermail/openroad-users/attachments/20061127/0dd6f218/attachment.html