• technologies
    Valoores In'Stant
    Introducing industry best practices to the architecture
    and infrastructure of the In'Stant project demonstrates
    our conscious efforts to ensure our products and services
    are compliant with any platform, any devise and any browser.
dev test architecture

Architecture and Infrastructure

Companies are looking to be ever competitive and stay well ahead of the competition. Valoores has mastered this by staying on top of the latest technology trends, and has been using these to deliver Intelligent Business Solutions to the banking Industry. Valoores is proud to announce to the Market the In'Stant project, this project is a revolution from architecture and infrastructure perspectives alongside with the solid and rich business core. Introducing industry best practices to the architecture and infrastructure of the In'Stant project demonstrates our conscious efforts to ensure our products and services are compliant with any platform, any devise and any browser.

Software Architecture

Spring:
The core of the In'Stant architecture is Spring, an IoC container. It delivers significant benefits to our applications and reduces development efforts while improving test coverage and quality.

Hibernate:
Hibernate ORM (Hibernate in short) is an object-relational mapping tool for the Java programming language. It provides a framework for mapping an object-oriented domain model to a relational database,it provides data query and retrieval facilities.

Kendo UI:
Kendo UI is a pure JavaScript framework with CSS defined for styling and behaviors. It is an end-to-end solution for modern client-side development

Software Infrastructure

In'Stant is a classical Java Web application relying on a database server, a Java application server, and an optional HTTP front-end. The application is accessed through a browser connected to the HTTP front-end or the application server through a TCP/IP LAN.

Scalability:
Both, the "Database Server" and "Application Server" make up what we call the "environment". Depending on the purpose of the environment (i.e. demonstration, mission critical application ...), the relevant components can be installed on a single hardware up to a set of highly redundant servers. Scalability can be achieved vertically (high-end servers with lots of resources), or horizontally (multiple clustered mid-sized servers). Deciding on the infrastructure depends on the importance of the application, budget, maturity and type of existing infrastructure, and cultural factors (like the influence of a dominant IT supplier).




technologies

Application Environment

Development: This environment is often managed by Soft Solutions' staff, where application patches are installed and tested before delivery to the client and can be located either at Valoores' premises or at the client's site.

Functional Testing: An environment used by Valoores and the client to test the newly received application, modules, and patches. Integration Testing: An environment used by Valoores and the client to test the inbound/outbound interfaces.

Training: Depending on the project organization, the training of the client's employees is either done on a functional testing environment or in a dedicated environment.

Pre-production: This is a mirror image of the production environment (i.e. in terms of connectivity for the interfaces, scheduling of the batches, software versions, etc.).

Production: This is the "live" environment typically used by end-users. Clustering technology can be used for reliability purposes. Alternatively, the pre-production environment could act as a backup.

Disaster Recovery: A separate environment is often located at a site away from the client's geographical data center location. The disaster recovery environment is used as a fallback in case of catastrophic problems at the production site. The technology used here is to keep the disaster recovery site synchronized with the production environment. The time needed to switch from one site to the other largely depends on the severity of the issues related to the system and on the available budget.

Sizing: When it comes to hardware sizing, various approaches can be taken: sizing according to similarities, start small and grow big over time, and timely estimates of the target architecture. When sizing according to similarities, choose a similar existing running application for reference of hardware size, functionalities, data volume and user base.




You have the VALUE,
we bring you the ADDED VALUE.
it's valoores!
Contact us