A Process Management System Based on Dynamic Service Management and Microservice Architecture

Abstract

The invention relates to a transaction management system based on dynamic service management and microservice architecture, developed for use in financial technology integrations, microservice architectures, API management, application integrations, and database integrations, offering comprehensive solutions for security and authorization.

Description

1 TARIFF A process management system based on dynamic service management and microservice architecture. The system TECHNICAL FIELD The invention is based on dynamic service management and microservice architecture in general. It is related to the transaction management system. The invention is particularly relevant to financial technology integrations, microservice architectures, and APIs. used in management, application integrations and database integrations Developed to offer comprehensive solutions in security and authorization. A process management system based on dynamic service management and microservice architecture. It is related to. 15 STATE OF THE ART Today, dynamic service management and microservice architecture are modern software technologies. It plays a significant role in development and distribution, especially in the finance sector. flexibility, scalability, and adaptability to rapidly changing business requirements. It is used for this purpose. Dynamic service management manages services in a software system. It plays a role in the continuous process of changing, optimizing, and improving its management. Traditional service management, on the other hand, generally involves fixed and predetermined structures. While limited, dynamic management environments can be much more flexible and adaptable. Micro 25 Service architecture, on the other hand, consists of small and independently operating software systems. It is structured to consist of services. Here, each microservice has a unique structure. It involves performing a function and generally managing a specific business process. In the current technology, dynamic service management and microservice architecture-based processes 30 Management systems manage an organization's business processes, workflows, and operations. It is used to manage efficiently. For example, an e-commerce site, products many areas such as sales, user accounts, payment processing, inventory management and logistics It can consist of microservices that manage different business processes. 2 The management system in the current technology is predefined in the static service architecture. Services and categories are not available, and code is needed for new service integrations. Changes are needed. Category-service mappings are inflexible and Service changes cannot be made during runtime. Dynamic DLL generation and... There is a missing loading information. There is no service record mechanism during operation. 5 Category-based service routing mechanism is not available. Transaction management It is not centralized. The static approach presents a scalability problem. New The system needs to be stopped and restarted for the categories. Category Service mappings are fixed within the code. In the classic scenario, the system is stopped, then a new one is created. The service is loaded, the code is updated, and the system is restarted. Because it's not flexible, 10 Management is equally difficult. These problems in current technology are especially challenging on a large scale. and leads to significant operational challenges in dynamic systems. As a result, improvements are being made to transaction management systems, therefore This will eliminate the disadvantages mentioned above and provide solutions to existing systems. New structures are needed to bring about this. THE PURPOSE OF THE INVENTION The present invention meets the aforementioned requirements and overcomes all the disadvantages of 20 It is related to the transaction management system, which eliminates these issues and brings some additional advantages. The main purpose of the invention is to integrate financial technology, microservice architectures, and APIs. used in management, application integrations and database integrations 25 developed to offer comprehensive security and authorization solutions. A process management system based on dynamic service management and microservice architecture. to provide. The structural and characteristic features and all the advantages of the invention are given in the figures below. And thanks to the detailed explanation written with references to these figures, it becomes clearer. 30 This will be understood as such. Therefore, the evaluation should also be based on these forms and details. This should be done taking the explanation into consideration. 3 BRIEF DESCRIPTION OF THE FIGURES The best way to utilize the advantages of the existing invention, together with its structure and additional elements. For understanding, it should be evaluated together with the figures explained below. is necessary. Figure 1 shows the block diagram view of the process management system that is the subject of the invention. 5 REFERENCE NUMBERS 1. Process Definition Module 2. Category control module 3. Code generation module 4. Compilation module 10 5. Registration module 6. Selection module 7. Credit service 8. Payment service 9. Banking service 15 10. Loading module 11. Transaction log module 12. Process execution module DETAILED EXPLANATION OF THE INVENTION 20 This detailed description explains the invention as dynamic service management and microservices. The preferred configurations for a process management system based on its architecture are, only to better understand the subject and without any limiting influence It is explained in a way that will not create. 25 The invention offers dynamic, comprehensive solutions in security and authorization. It is a process management system based on service management and microservice architecture. System;  Create a new transaction record for the desired operation. a process definition module (1), 4  The transaction created by the mentioned transaction definition module (1) A category check that determines which service it should be associated with. module (2),  If the category control module (2) detects a new category, it will be dynamic. a code generation module (3), 5  The code generated by the mentioned code generation module (3) is a DLL a code compilation module (4) that compiles in the format  Credit service for credit transactions according to the identified category of the transaction. (7), payment service for payment processing (8) and banking transactions banking service (9) including the redirecting service selection 10 module (6),  A service loading module (10) that loads DLL code to the selected service.  Code loaded by the service loading module (10) a transaction log that creates a transaction record to enable its execution module (11) and 15  a process execution module that runs the recorded process (12) It includes. The system described in the invention, shown in the block diagram in Figure 1, is used in banking. financial systems, payment systems, insurance systems and credit systems, etc. In technology integrations; dynamic service management, service orchestration and In microservice architectures such as distributed systems; dynamic API management, API In API management, such as categorization and service integrations; enterprise systems, In application integrations such as ERP systems and workflow systems; NoSQL systems (MongoDB), DLL (Dynamic Link Library) management and dynamic code generation 25 It is designed for use in database integrations such as database management. The operating principle of the system described in the invention is given in a sample application as follows: A process management system based on dynamic service management and microservice architecture. In the system, firstly, at the start of the process, a process definition module (1) is used by 30 A new transaction record is created and how the transaction will be managed is determined. A category The control module (2) determines which service the process will be associated with. This check is performed. If it is a new category, the code generation module (3) Dynamic code is generated. If it is an existing category, it is pre-generated code. It is compiled by the compilation module (4) in DLL (Dynamic Link Library) format and The database is registered by the registration module (5). After compilation, the service three different routings according to the category of operation by the selection module (6) The following are done: credit service for credit transactions (7), payment service for payment transactions. (8) and banking service for banking transactions (9). Upload module 5 to the selected service. DLL code is loaded by (10). Transaction log module (11) logs the transaction. The process tracking on the service is initiated by creating the system. Finally, the process execution begins. The operation recorded by module (12) is being executed. Thanks to the system described in the invention, new categories can be dynamically created for each process. It can be added. Code in DLL format is executed at runtime. It can be loaded and managed. Selected operations are automatically categorized accordingly. It can be managed in this way. Microservice architecture provides scalability. The invention allows for flexibility, scalability, and the use of all elements within the system. A manageable structure is provided. Each component fulfills its own responsibility. 15 During this process, the entire system works in a coordinated manner. At every step of this process... The process proceeds using the output from the previous step, and the entire process is managed automatically. The category control and service selection stages, in particular, highlight the dynamic nature of the system. These are the critical points that are revealed. The system described in the invention essentially consists of four layers: the production of processes, a process management layer for compiling and storing; category management and Category management layer for matching with services; (Credit, Payment, Banking) service layer for different integration services such as these, and finally data persistence. A storage layer for storing data. In summary, the first step is processing 25 It is created and category identification is made. If it is a new category, the category is created; If it's an existing category, its settings are loaded. Then DLL generation takes place, and It is saved. The appropriate service is selected according to the category type. The DLL is loaded in the selected service. The process is recorded and executed. This flow is part of the system's dynamic and automated process management. It reveals its characteristic. 30 The invention describes the microservice perspective of the system's runtime behavior. It shows the loading of DLLs and category mapping at the service registry layer. This happens. In the transaction execution layer, transactions are executed and managed. 6 At the monitoring layer, the system's performance and status are tracked. Data management. The perspective shows the data flow and management within the system. In the transaction data section... Basic process definitions and categories, service configurations in the Service Data section. and matching, while the monitoring data section includes system performance and statistics. It is managed. 5 The preferred configuration of the system in question is JWT-based token validation. The mechanism ensures the security of all API requests, while role-based access Detailed authorization management is performed using the Control Center (RBAC) system. All communication is secured using SSL / TLS encryption, and Every transaction is logged in detail, providing a complete audit trail. Performance 10 And in terms of scalability, the system incorporates all the features of modern microservice architecture. It takes advantage of its benefits. Thanks to its support for both horizontal and vertical scaling. It can instantly adapt to the increasing workload, and resources are managed with automatic load balancing. It is used optimally. Advanced cache management and asynchronous processing. High performance is ensured with the support of health check and automatic recovery 15 System continuity is guaranteed through these mechanisms. Integration In terms of capabilities, the system will meet all the needs of the financial sector. It is designed in this way. In addition to REST and SOAP protocols, it also supports standard banking. The protocols, ISO20022 and SWIFT message formats are fully supported. Real-time communication is enabled with WebSocket support, while batch processing capabilities are 20. With this system, bulk operations can be managed effectively. In terms of monitoring and management... The system offers comprehensive metric collection and analysis capabilities. Real-time System performance can be continuously monitored and alarms can be triggered using dashboard and reporting tools. And with notification mechanisms, potential problems can be addressed immediately. Dynamic service management is provided through service discovery and registry mechanisms, 25 System configuration is effectively controlled through centralized configuration management. This is possible. In terms of business continuity, the system offers high availability (HA) and disaster recovery. It is equipped with recovery capabilities. Automatic backup and restore mechanisms, with circuit breaker pattern implementation, retry and fallback mechanisms. Uninterrupted service delivery is guaranteed. The system uses modern DevOps 30. It fully supports their practices. CI / CD pipeline support, automated testing, and deployment processes, Infrastructure as Code (IaC) support, and Kubernetes with compatibility with modern development and operational processes effectively It is manageable. With comprehensive API documentation and testing tools, developers can... 7 The level of expertise is kept at a high level. Regarding regulatory compliance, the system is under the supervision of the Banking Regulation and Supervision Agency (BDDK). regulations, KVKK / GDPR data protection requirements and PCI-DSS standards It is designed to ensure full compliance. Detailed audit and compliance. reporting capabilities and compliance with regulatory requirements are ensured. It has been acquired. As part of advanced capabilities, the system includes a dynamic business rules engine, 5 Complex event processing, AI / ML model integration, and big data. It offers analytical capabilities. With blockchain integration support, it promises the future. An infrastructure ready for financial technologies is provided. Operational efficiency. In terms of system, self-service portal, low-code / no-code development tools, automated It offers service provisioning and comprehensive troubleshooting tools. For detailed information, see 10. operational processes are effectively managed through database and documentation management. It is manageable. As part of future expansion plans, the system includes open banking. standards support, adaptation to new financial technologies, multi-cloud support for future features such as edge computing capabilities and quantum-safe cryptography. It offers an infrastructure ready for today's technologies. Thanks to this, the system is not only compatible with today's 15 not only, but also a comprehensive financial technology that can meet the needs of the future. It is positioned as a platform with this broad skill set and future vision. Thanks to the system described in the invention, all the needs of the modern financial sector can be met. A safe, scalable, and sustainable platform is offered that can meet these needs. Its flexible architecture can adapt to constantly evolving technology and changing needs. 20 It is designed as a long-term solution.

Claims

8 REQUESTS 1. A process management system based on dynamic service management and microservice architecture. It is a system, and its feature is;  Create a new transaction record for the desired operation. 5 a process definition module (1),  The transaction created by the mentioned transaction definition module (1) A category check that determines which service it should be associated with. module (2),  If the category control module (2) detects a new category, dynamic 10 a code generation module (3),  The code generated by the mentioned code generation module (3) is a DLL a code compilation module (4) that compiles in the format  Credit service for credit transactions according to the identified category of the transaction. (7), payment service for payment processing (8) and 15 for banking transactions banking service (9) including the service selection that directs module (6),  A service loading module (10) that loads DLL code to the selected service.  Code loaded by the service loading module (10) a transaction log that creates a transaction log to enable its execution 20 module (11) and  a process execution module that runs the recorded process (12) It includes.

Images