time@work has been designed from the ground up as an Enterprise Application capable of supporting thousands of users and the many hundreds of thousands of resulting transactions. Built on .NET technology standards, time@work meets the most stringent security, reliability and scalability performance criteria.
This paper deals with time@work’s scalability credentials, focusing on how its architectural framework has been designed with scalability in mind.
“Scalability is all about Systems Architecture”
Scalability is the capability to increase resources in order to yield a linear increase in service capacity. Put another way, scalability is the capacity to handle additional users or transactions without fundamentally altering the application’s architecture or design.
In designing time@work to be truly scalable, steady performance is achieved by adding additional resources such as servers or memory as the load increases. While other factors do come into play, when we talk about time@work being a truly scalable application we have sought to achieve a direct or linear relationship between the amount of resources added and the resulting increase in performance.
The foundations of this scalability were laid in the design of time@work’s Systems Architecture. By using Microsoft’s .NET technologies, time@work has been built using solid object-oriented techniques and developed as a scalable n-tier application.
Because time@work has been developed using VB.NET and ASP.NET it benefits from the framework in a number of key areas:
4. Ease of Deployment
time@work has been designed with scalability in mind and by using ASP.NET it benefits from features specifically tailored to improve performance in clustered and multiprocessor environments.
In addition, processes are closely monitored and managed by the ASP.NET runtime, so that if one misbehaves (such as leaks or deadlocks), a new process can be created in its place, which helps keep time@work constantly available to handle requests.
At the heart of time@work’s architectural framework is an integrated, standards driven philosophy that enables users to work, collaborate and run their business in real time.
Its highly configurable and flexible design allows deployment of time@work as a true, multi- company, multi-language and multi- currency application.
By designing time@work with a zero footprint client, its setup, deployment, and administration can all be handled centrally with no requirement for modifications on the client side. The result is a true web enabled application which enables your employees to access and manage their forms from anywhere.
Some of the key components of time@work’s architectural framework are:
1. SQL Server Database
2. XSL & XML where appropriate
3. Zero footprint deployment
4. Flexible reporting and BI engine
5. Powerful workflow engine
6. Robust security engine
The database engine used to power time@work is Microsoft SQL Server. SQL Server has been designed as an industrial strength RDBMS and delivers scalability for e- commerce, data warehousing, and line-of-business solutions.
Independent benchmark testing has shown that SQL Server can handle over 700, 000 transactions per minute (709, 220 to be precise!) and has established its position as one of the fastest databases in the world. On the Transaction Processing Performance Council (TPC) TPC-C performance list, SQL Server and Microsoft Windows® 2000 hold three of the top five Clustered TPC-C results.
By utilising browser technology as its delivery mechanism, time@work’s user interface is simple to use, easy to customise, rapidly deployable and highly scalable.
Its secure, role-based flexibility and intuitive interface enables organisations to achieve rapid and painless user acceptance and to roll out time@work with the minimum of training. Its zero footprint design enables fast and painless deployment for tens, hundreds or thousands of users.
One of the most powerful aspects of time@work’s scalability is in the design and optimisation of its data structure and reporting engine.
time@work’s sophisticated calculation algorithms are optimised to avoid excessive data access by using advanced caching techniques to store control and configuration data.
time@work allows the construction of alternative index’s which greatly improves reporting speed for key management reports.
Reports will monitor their own performance efficiency thus enabling administrators to see how many records have been accessed and how long it took to access them. The alternative indexing features of time@work can then be utilised to enhance reporting speed.
time@work’s integration framework and XML capabilities enables organisations to exchange real time data with other enterprise applications such as CRM and Financial Systems. Using XML, time@work’s data structures can be passed among processes in distributed environments providing a more flexible and neutral communication medium than binary solutions such as RPC and CORBA.
As an enterprise enabled application capable of supporting many thousands of users, time@work was designed with a highly configurable and robust security engine at the heart of its business logic. In addition, time@work avails of the considerable security capabilities inherent in SQL Server.
To be able to access time@work data a user must pass through two stages of authentication, one at the SQL Server level and the other at the database level.
These two security levels are implemented using logins names and user accounts respectively. A valid login id and password enables time@work to connect to the SQL Server and a valid login id is required to access an time@work database.
During a new connection request, SQL Server verifies the login name supplied using either Windows authentication mode and Mixed mode.
Within the time@work application itself, further security is available to the Systems Administrator.
time@work has been designed with scalability in mind both at the application and architectural level. This design philosophy allows organisations to address their business needs in a timely fashion, and addresses the cost concerns of running a powerful application such as time@work within the their existing and future IT infrastructures.