Unified development method for automobile finance business

Abstract

The application discloses a unified development method for automobile financial service, comprising the following steps: defining and constructing a common development component model of the service, while supporting customized configuration; constructing a core model in conformity with daily financial service for interaction based on the common development component model; loading and uploading start configuration information to a CFP registration center, and sequentially registering each service to change into a distributed micro-service application, uploading relevant monitoring data to a CFP service monitoring platform through a sentinel client, and embedding a relevant service interface through a sentinel mechanism; taking the core model as the center, deriving various derived component models required in the service development process according to actual requirements, and performing secondary encapsulation of the configuration through a bottom component; and importing required model components on demand, and shielding non-service attributes. The method is helpful for coping with requirements, maintaining unity, reducing cost and improving efficiency; optimizing an internal system, and better guaranteeing safety and assisting in analyzing faults.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of automobile financial business development, in particular to a unified development method of automobile financial business. BACKGROUND

[0002] With the rapid development of the Internet, new technologies are emerging, and at the same time, a large number of new business models are also emerging. Among them, the automobile financial field has gradually begun to use the power of the Internet to quickly expand its business, and generally takes business-driven technology as the development direction to meet the needs of users to buy cars on loan.

[0003] However, most of the technology-related needs of automobile financial companies are realized by outsourcing foreign systems, which does not meet the trend of localization; or by third-party manufacturers, resulting in an increasing number of old systems with outdated technology and inconsistent technology stacks, thereby causing high learning costs, difficulty in maintaining systems, and difficulty in recruiting employees to match the positions. In this way, not only will the process of business-driven technology be hindered, but also new models cannot be developed through technology-driven business.

[0004] Therefore, there is an urgent need to provide a new unified development method of automobile financial business to solve the above problems. SUMMARY

[0005] The purpose of the present application is to provide a unified development method of automobile financial business, which first helps enterprises to cope with the rapid development of business needs and maintain style consistency, reduce company management costs, and significantly improve development efficiency; secondly, optimizes the enterprise internal training, operation and maintenance, and examination system; at the same time, it can better guarantee the safety in the process of business and assist in analyzing the existing faults.

[0006] In order to achieve the above purpose, the present application provides a unified development method of automobile financial business, which comprises:

[0007] S1, defining and constructing a common development component model of business, including common parameter configuration of each business system, while supporting customized configuration;

[0008] S2, based on the common development component model in step S1, a core model conforming to the daily financial business for interaction is constructed; then, the start configuration information is loaded and uploaded to the CFP registration center, each service is registered in turn to change into a distributed micro-service application, and the related monitoring data is uploaded to the CFP service monitoring platform through the sentinel client, thereby having system monitoring capability and calculating system risk value in real time; the related business log is built into the component model, thereby automatically generating and having log collection capability without configuration; the related service interface is embedded with the sentinel mechanism, thereby automatically having default flow limiting and fusing capability without configuration;

[0009] S3, centering on the core model in step S2, deriving various message, cache, code generation, sequence, business image, file and other derived component models required in the business development process according to actual needs, and the configuration is encapsulated again through the underlying components, so that the service can automatically connect to the corresponding middleware components after starting, and provide interaction capabilities with various middleware. This process does not require additional configuration information;

[0010] S4, importing the required model components on demand, shielding non-business attributes, and quickly developing related functions of automobile financial business in sequence through simple calling.

[0011] Preferably, the core model in step S2 is implemented by the following steps:

[0012] Firstly, through the automatic configuration technology of Springboot, the corresponding environment is identified after the project starts, the corresponding registration center address is read and service registration is performed, so that the service is changed into a distributed microservice, and node expansion, unified parameter modification and hot deployment are supported;

[0013] Secondly, the risk index collection task is started, that is, the risk index value is collected and uploaded to the service monitoring platform in a timely manner, and the system risk value is calculated in real time by the service monitoring platform, and the system with high risk value is monitored and alarmed in real time;

[0014] Then, according to the default log configuration, the automatic log collection is started from the aspects of system, service, database, message and business by using aspect and template method, which is used to automatically collect various log information generated in the running process of the business system;

[0015] Finally, taking financial business data as input, combining with the general component capability, in the form of abstract template method, the input is processed and constructed according to the specified steps and a consistent interface access is provided to the outside, combined with the middleware capability, automatically supporting the processing capability of complex distributed application program, as a carrier of business data, further processing various customer outputs and unified feedback.

[0016] Preferably, the calculation of the system risk value comprises:

[0017] The risk indicators are classified and defined from the two dimensions of development and operation, and each risk indicator is assigned a weight, and the risk indicator value is collected and calculated in a timely manner during the system running process:

[0018]

[0019] Wherein, Rc represents the total risk value of the system, R n represents each risk indicator input in advance, w n represents the risk weight assigned to each risk indicator; the larger the Rc value obtained by calculation, the higher the system risk value.

[0020] According to the technical solution, the application proposes a unified development framework scheme for the development mode of the traditional automobile finance field, adopts mainstream technology to avoid the problem of outdated technology by means of the open source power of the Internet and in combination with the automobile finance industry, adopts independent development to reduce the introduction of foreign product systems, and sets cluster deployment for general component capability and middleware capability from the aspects of robustness and consistency, adopts a unified development technology stack, and tries to be light and non-intrusive to make development convenient, practical, safe and reliable.

[0021] Other features and advantages of the present application will be described in detail in the following specific embodiments. BRIEF DESCRIPTION OF DRAWINGS

[0022] The accompanying drawings are included to provide a further understanding of the application, and constitute a part of the specification, and are used together with the following specific embodiments to explain the application, but do not constitute a limitation on the application. In the drawings:

[0023] Figure 1 is a unified development framework flowchart in a unified development method of an automobile finance business provided by the application. DETAILED DESCRIPTION

[0024] The specific embodiments of the application will be described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are only used to illustrate and explain the application, and do not limit the application.

[0025] Referring to Figure 1 , the application provides a unified development method of an automobile finance business, which comprises:

[0026] S1, defining and constructing a common development component model of the business, including common parameter configuration of each business system, while supporting customized configuration;

[0027] In the application, the specific content of the common development component model comprises automobile finance business constants, environment variables, department classification constants, unified business error codes, common message codes, error code interfaces, basic business exceptions, unified business runtime exceptions, unified log printing, unified request and response classes, and general business tool classes.

[0028] S2, based on the public development component model in step S1, a core model conforming to the daily financial business for interaction is built; then, the start configuration information is loaded and uploaded to the CFP registration center, each service is registered in turn to become a distributed micro-service application, and the related monitoring data is uploaded to the CFP service monitoring platform through the sentinel client, so that the system monitoring capability is obtained and the system risk value is calculated in real time; the related business log is built in the component model, so that the log collection capability is automatically generated without configuration; the related service interface is embedded with the sentinel mechanism, so that the default flow limiting and fusing capability is automatically obtained without configuration;

[0029] In the application, the core component model specifically comprises: registration center automatic configuration, monitoring configuration, flow limiting and fusing default configuration, micro-service annotation, DDD domain model conversion tool, business template, business filter, interceptor, unified business context and unified parameter verification.

[0030] S3, according to actual needs, various message, cache, code generation, sequence, business image, file and other derived component models required in the business development process are derived from the core model in step S2, and the configurations are encapsulated again through the underlying components, so that the corresponding middleware components can be automatically connected after the service is started, and the interaction capability with various middleware is provided, and this process does not require additional configuration information;

[0031] In the application, the derived component model contains a large amount of middleware capability and the capability customized for the automobile financial business, and mainly comprises: image component, database component, serial number component, distributed cache component, message component, code generation component, file system component, log component, business security component and third-party interface component.

[0032] S4, the required model components are imported on demand, the non-business attribute is shielded, and the automobile financial business related functions can be developed quickly in turn by simple calling.

[0033] The core model in step S2 is implemented through the following steps.

[0034] Firstly, through the automatic configuration technology of Springboot, the corresponding environment is recognized after the project is started, the corresponding registration center address is read and the service is registered, so that the service is changed into a distributed micro-service, and node expansion, unified parameter modification and hot deployment are supported;

[0035] Secondly, a risk index collection task is started, that is, the risk index value is collected and uploaded to the service monitoring platform in a timely manner, the system risk value is calculated in real time by the service monitoring platform, and the system with a high risk value is monitored and alarmed in real time;

[0036] Next, based on the default log configuration, automatic log collection is enabled from the perspectives of system, service, database, message, and business using aspects and templates. This is used to automatically collect various log information generated during the operation of the business system.

[0037] Finally, using financial business data as input and combined with general component capabilities, the input is processed and constructed according to specified steps in the form of an abstract template method, and consistent interface access is provided to the outside world. Combined with middleware capabilities, it automatically supports the processing capabilities of complex distributed applications. As a carrier of business data, it is further processed into various customer outputs and unified feedback.

[0038] The above calculation system risk value includes:

[0039] Risk indicators are defined and entered from the two dimensions of development and operation and maintenance, and weights are assigned to each risk indicator. Risk indicator values ​​are collected and calculated regularly during system operation:

[0040]

[0041] Among them, Rc represents the total risk value of the system, R n Represents each pre-entered risk indicator, w n Represents the risk weight assigned to each risk indicator; the larger the calculated Rc value, the higher the system risk value.

[0042] In summary, the present invention takes into account the business characteristics of financial companies. From the perspective of robustness and consistency, both general component capabilities and middleware capabilities are equipped with cluster deployment, and the unified development template is as lightweight and non-invasive as possible, making development convenient, practical, safe and reliable.

[0043] This shows that the unified development approach for auto finance business first helps companies cope with rapidly growing business needs, maintain a unified style, reduce corporate management costs, and significantly improve development efficiency. Second, it has a positive and effective impact on the company's internal training, operation and maintenance, and assessment systems. Third, through the system risk value, combined with risk indicators and weights, each business system can be accurately monitored and calculated in real time, which can better ensure the security of the business process and assist in the analysis of existing faults.

[0044] The preferred embodiments of the present invention are described in detail above in conjunction with the accompanying drawings. However, the present invention is not limited to the specific details in the above embodiments. Within the technical concept of the present invention, various simple modifications can be made to the technical solution of the present invention, and these simple modifications all fall within the scope of protection of the present invention.

[0045] It should be further noted that the various technical features described in the above detailed description can be combined in any suitable manner without departing from the scope of the application. To avoid not necessary repetition regarding various combinations, no further combinations will be described.

[0046] Moreover, the various embodiments described herein can be combined in any suitable manner, as long as such combinations do not depart from the scope of the present application.

Claims

1. A unified development method for automobile finance business, characterized in that: The method comprises: S1. Define and build a common development component model for all businesses, including common parameter configurations for each business system, while supporting customized configurations; S2. Based on the public development component model in step S1, a core model for interaction that meets the needs of daily financial business is constructed. Then, the startup configuration information is loaded and uploaded to the CFP registration center. Each service is registered in turn and transformed into a distributed microservice application. The relevant monitoring data is uploaded to the CFP service monitoring platform through the Sentinel client, thus providing system monitoring capabilities and real-time calculation of system risk values. The relevant business logs are built into the component model, so they can be automatically generated without configuration and have log collection capabilities. The relevant service interfaces have the default current limiting and circuit breaking capabilities automatically without configuration through the embedded Sentinel mechanism. S3. Based on the core model in step S2, derived component models for various messages, caches, code generation, sequences, business images, and files required during business development are derived according to actual needs. All configurations are re-encapsulated through the underlying components. After the service is started, it automatically connects to the corresponding middleware components and provides the ability to interact with various middleware. This process does not require additional configuration information. S4. Import the required model components on demand, shield non-business attributes, and quickly develop auto finance business-related functions one by one through simple calls; The core model in step S2 is implemented by the following steps: First, through Springboot's automatic configuration technology, the corresponding environment is identified after the project is started, the corresponding registration center address is read, and the service is registered, so that the service is transformed into a distributed microservice, and node expansion, unified parameter modification, and hot deployment are supported; Secondly, start the scheduled risk indicator collection task. This means regularly collecting risk indicator values ​​and uploading them to the service monitoring platform. The service monitoring platform calculates the system risk value in real time and monitors and issues alerts for systems with excessively high risk values. Next, based on the default log configuration, we use aspects and templates to enable automatic log collection from the perspectives of system, service, database, message, and business. This is used to automatically collect various log information generated during the operation of the business system. Finally, using financial business data as input, combined with general component capabilities, and in the form of abstract template methods, the input is processed and constructed according to specified steps and a consistent interface access is provided externally. Combined with middleware capabilities, it automatically supports the processing capabilities of complex distributed applications. As a carrier of business data, it is further processed into various customer outputs and unified feedback. Calculating the system risk value includes: Risk indicators are defined and entered from the two dimensions of development and operation and maintenance, and weights are assigned to each risk indicator. Risk indicator values ​​are collected and calculated regularly during system operation: in, represents the total system risk value, Represents each pre-entered risk indicator, Represents the risk weight assigned to each risk indicator; the calculated The larger the value, the higher the system risk value.

Images