APPLICATION ARCHITECTURE eBank.net architecture follows service-oriented multi-tier design.
A permanently available database stores eBank.net users’ records, temporary bank information and additional system information.
Application services tier implements eBank.net business and application logic. Most of generic business processes provided by application services are available as XML Web Services.
Front-end and channel interfaces are loosely dependent on application services tier and allow easy re-design following bank’s requirements and channel-specific features.
Integration tier that handles data flow between eBank.net and Bank information systems is customized, tuned and tailor-developed for every particular Bank system.
Component design allows flexible deployment configurations where eBank.net components are hosted on shared or dedicated servers depending on specific cases.
In eBank.net development a balanced approach have been applied - high-level platform independent technologies (such as XML) are used for user interfaces and inter-system communication, while core modules are implemented in high-performance low-level programming style (C++, etc.).
The following diagram illustrates eBank.net simplified architecture concept and outlines main application domains and component groups. (Note: No physical design issues are presented except for information transport between application domains).
Diagram. Simplified eBank.net conceptual diagram