Distributed Architecture

rPay.net has been designed using a distributed, object-oriented architecture, meaning that it uses object-oriented design and programming concepts to define a logical n-tier architecture. An application built following this architecture can be easily configured to run in various physical n-tier configurations. This framework simplifies the development of business applications in a complex distributed environment.

The rPay.net architecture:

• Allows our application to run as an Internet or Extranet application with no programming changes. rPay.net can run as 3, 4, or 5 physical tiers without any programming changes.
  
• Is very scalable. It supports web server farms.
  
• Is designed where the User Interface layer is cleanly separated from the Business Logic layer, allowing us to support different front ends, such as NSCC/DTCC, TXLifE/XMLifE, AOE, and web services.
  
• Includes support for batch and reporting programs in the design.
  
• Includes an easy to understand Object-Oriented design.
  

3, 4, and 5 Tier Architecture

The rPay.net framework is designed as a true 5-tier architecture where there is separation of functionality into clearly defined roles or groups, in order to increase clarity and maintainability. The framework can be configured into various physical architectures to achieve optimal results for Windows Forms, Web Forms and web services forms. Configuring the framework into one, two, three, four or five physical tiers allows us to gain performance, scalability, security or fault-tolerance to various degrees and in various combinations.

It should be noted that even though the system is designed with 5 logical tiers, in reality only 3 or 4 physical tiers will be utilized. Changing the number of physical tiers is accomplished through the use of a configuration file.

5-Tier Logical Architecture