ISIS Papyrus Software

Handling Enterprise Growth Without Java

In scalability on October 22, 2009 at 2:02 am

With many Papyrus Platform installations experiencing substantial growth the topic of application scalability has come to the foreground. Owing to its design the scalability of the Papyrus Platform is unlimited in principle but it is restricted by certain synchronicity needs. Simply reading or displaying documents or content from storage has no limitation, but keeping multiple write accesses in sync creates scalability issues. Clearly, when the number of users is doubled from 1,000 to 2,000 users then it does require monitoring and, if necessary, scaling of the hardware. When the number of documents or process tasks is doubled from 1,000 to 2,000 per hour that also requires consideration how that load can be safely spread across server nodes. However, scaling Papyrus Platform applications is very simple compared to, for example, three-tiered Web/Java/SQL/SOA application clusters, explains Max J. Pucher, Chief Architect at ISIS Papyrus.

User complaints about a ‘slow application’ without any measurable details do not really help, yet have to be carefully considered. Users are often unaware of different processing requirements for documents looking rather similarly. The document might be simple for the user but the back-end process can be fairly complex and proactive monitoring is advised, which Papyrus Platform provides with easy-to-use dashboards and summary reports.

Scalability is not only about tuning or maintaining an acceptable response time for a growing number of users. It is unreasonable to expect that the system will handle growth in users and transactions automatically. No system does. Papyrus has many load balancing and tuning options and many are set either by default or by the system. Document applications are a complicated conglomerate of GUI, process, and rule execution threads that read and write data from a number of service interfaces or databases. The performance of the SOA back-end service interfaces or the database is much more relevant to the scalability than the user front-end. Using common database or transaction measurements the Papyrus Platform executes millions of transactions per hour and provides substantially simplified systems management and tuning without neglecting the user experience.

About these ads
Follow

Get every new post delivered to your Inbox.

Join 1,889 other followers

%d bloggers like this: