Processing and Scalability

End of Day (EOD) is the key processing module within the AXCESS™ system. The AXCESS™ EOD processing module utilities a grid processing system which can take advantage of any spare processing power available across the network. AXCESS™ EOD also has a separate Task processor service and a separate Transaction processor service.

AXCESS™ allows the system administrator to setup multiple Task and Transaction Processors to cater for increased processing volumes. When EOD is invoked, AXCESS™ tasks queued for that day, are passed to the Service Grid Processing service.

This service routes the queued tasks and transactions to the Task and Transaction Processors. When multiple processors are invoked, the Service Grid Processor will load balance across the multiple processors. There is always only one instance of the Service Grid Processor running.

The AXCESS™ architecture enables these Task and Transaction processors to be deployed onto separate servers and separate processors.

For example a cluster of three servers can be configured with each server running one Task Processor and one Transaction Processor. The Service Grid Processor will load balance across these three servers. This will allow one server’s processors, as an example, to generate interest calculations, the second one to generate statements and the third server to generate reports.

As volumes grow the system is scaled by adding more servers to the processing grid. This eliminates the typical linear approach of most applications and truly optimises the processing power of the grid. In testing conducted “In house” on “bottom end” scale processing servers a validated increase in performance of at least 25% to 30%. In migrating to a clustered Blade environment, using the latest in Quad Core Processing technology, that performance will increase significantly.

Service Oriented Architecture

When developing the Service Grid Processing structure within AXCESS™ we sought to position the solution well ahead of other financial product management solution providers with respect to fulfilling the objectives of Service Oriented Architecture (SOA). Recent moves by MicrosoftTM and SAPTM to form Banking Industry Architecture network (BIAN)1 in Europe along with several large financial institutions validates this approach. The object of BIAN is to create solutions focused on SOA for Banks and related financial institutions. AXCESS™ already meets the core requirements here on many levels.

The text book definition of SOA is a software architecture where functionality is grouped around business process and is packaged as inter-operable services. SOA also describes IT infrastructure which allows different applications to exchange data with one another as they participate in the business process. The aim is a loose coupling of services with operating systems, programming languages and other technologies which underlie applications.

  1. SOA separates functions into distince units or services.
  2. These are made accessible over a network in order that they can be combined and reused in the production of business applications.
  3. These services communicate with each other by passing data from one service to another or by coordinating an activity between two or more services.
  4. SOA concepts are often seen as built apon and evolving from older concepts of distributed computing and modular programming.

Distributed computing in reference to SOA deals with hardware and software systems containing:

  1. More than one processing element or storage element.
  2. Running concurrent processes.
  3. Or multiple programs, running under a loosely or tightly controlled regime.

In distributed computing a program is split up into parts that runs simultaneously on multiple computers communication over a network. Whilst Distributed computing is a form of parallel computing, the term parallel computing is most commonly used to describe program parts running simultaneously on multiple processors on the same computer. Both types of processing require dividing a program into parts that can run simultaneously, but distributed programs often must deal with heterogeneous environments, network links of vary latencies and unpredictable failures in the network or the computers.

In effect the segmentation of processes within AXCESS™ helps us to achieve this effectively. In reviewing the solution we then add other key elements to the equation including:

  • That AXCESS™ is developed on .NET Framework, which makes ease of integration with virtually any solution a reality
  • AXCESS™ Client Relationship Management (CRM) foundation, insures a truly customer centric environment.
  • Integrated reporting capabilities that can report on any field, in a text or graphical nature, Takes data mining to a new level.
  • Workflow tools that allow mapping and/or adjusting of business processes without any programmer intervention.
  • Dynamically integrated web client that allows content management and effective client collaboration.

When all of this is taken into account the structure meets and in many ways exceeds much of what SOA implementations attempt to achieve.

Real time load data as well as EOD data is available from Axcess Consulting Group Pty Ltd.