GPI Framework
The Capsys General Process Interface (GPI) is an application and microservices platform designed for data collection, processing, and forwarding, used by numerous domestic and international financial institutions and service providers. GPI supports critical infrastructure with 24/7 operation. We consider it a priority to develop GPI independently, not only based on client requirements but also taking into account market trends and technological expectations. Besides business functionality, ensuring high availability is a key focus; therefore, GPI can run autonomously, on various application servers, or even in Docker environments, tailored to the client’s infrastructure and demands.
GPI Framework Integration Component
The GPI framework enables the connection of non-harmonized systems and interfaces. It serves as an integration component allowing both online and offline communication between internal systems and integration layers. The core component supports various synchronous and asynchronous communication capabilities. Its responsibilities include transforming and logging inbound and outbound messages, ensuring data integrity (e.g., eliminating duplicates), and allowing the expansion of new system connections post-deployment. Orchestration logic and translation between message formats and protocols are implemented within this layer.
Key Features of GPI:
- Flexible Service: Thanks to its design and scalability, it can flexibly meet diverse technical requirements.
- Communication Capabilities: Supports synchronous calls (e.g., REST, SOAP) and asynchronous calls (e.g., MQ) both for sending and receiving.
- Automatic Connection Recovery: If the database or any external connection breaks, the application suspends affected channels until the connection is restored.
- Intervention-Free Restart: After connection restoration, channels automatically restart (channels manually stopped or excluded from auto-restart remain inactive).
- Comprehensive Logging: Logs are archived depending on configuration and environment.
GPI Lifecycle
GPI is developed as an independent product, driven by customer needs as well as market trends and technological expectations. Alongside business functionality, high availability remains a priority. The system can run independently on various application servers or in Docker environments. The use of a DSL within the framework allows modification of message formats, provided the client has appropriate permissions.
Quality Assurance
Ensuring the product quality of GPI is critical for such a vital system component. The adopted development methodology—feature branching—ensures that untested code cannot be included in GPI’s release builds, thus preventing faulty code from being delivered. After a build is created for the client, mock applications and developer tests for GPI are automatically deployed to the necessary Docker environments. Subsequently, automated general functional tests run, generating test documentation that certifies the correct functioning of features.
