Architectural additions

These are some features that are not at all implemented and are core architectural changes. These go beyond what can be done with existing code base.

• High availability of server

On drawback of multithreaded server is that a faulty plugged-in application can take down entire server.

To avoid this pitfall, when server is started, it is forked off in separate processes. One process can monitor the worker instance and can be used for reporting purposes. In case the worker instance crashes, monitoring instance can restart it.

Since no plugged-in application will be running in monitoring instance, it will guaranteed that the server and application will be available all the time. However if an application is really buggy, this will lead to countless restart and could be problematic. Hence a configuration parameter is introduced that allows to limit maximum number of restarts of an application.

• On the fly maintenance

A planned feature in this server is to manage every resource including client application on the fly. Reloading the client application without restarting the server would be a great advantage over other server applications.

• Clustering

  In order to cluster-enable OAS, we need to implement some basic functionality such as

  • Distributed locking
  • Distributed data transfer protocols
  • Distributed maintenance protocols

Although these features are not required immediately, these are absolute must to implement an enterprise solution.