CN109710236B

CN109710236B - Service development and implementation method, device, platform and medium based on shared service

Info

Publication number: CN109710236B
Application number: CN201811648448.9A
Authority: CN
Inventors: 高峰
Original assignee: Beijing ByteDance Network Technology Co Ltd
Current assignee: Beijing ByteDance Network Technology Co Ltd
Priority date: 2018-12-30
Filing date: 2018-12-30
Publication date: 2022-04-05
Anticipated expiration: 2038-12-30
Also published as: CN109710236A

Abstract

The embodiment of the disclosure discloses a method, a device, a platform and a medium for developing and realizing services based on shared services. The method comprises the following steps: attribute configuration information input by a shared service module in the development process of a target service program by a service developer is obtained; and generating a shared service code instance and a configuration file for the target business program to call according to the attribute configuration information, the code template of the shared service module and the automatic programming rule. The technical scheme of the embodiment of the disclosure can reduce the workload of repeated development of the common service function by different service developers, improve the expandability of the shared service, and also can give consideration to the universality and the individual service requirements of the shared service function.

Description

Service development and implementation method, device, platform and medium based on shared service

Technical Field

The disclosed embodiments relate to the technical field of computer program processing, and in particular, to a method, an apparatus, a platform, and a medium for service development and implementation based on a shared service.

Background

With the popularization of intelligent terminals, various types and functions of application software are produced. In order to meet the use requirements of users, more and more application software can support various rich service functions.

Due to different factors such as the core business function of the application software, the user population and the like, the requirements of different application software on various service functions are not completely the same. Therefore, the application software of each business function respectively carries out development work supporting the business function logic of the application software, and personalized definition can be carried out on the service functions with commonalities in each business according to business requirements, and the development is completed. With the capability of meeting the personalized use requirements of businesses for service functions, however, different business teams can perform a lot of repeated development work.

In the research process of the present disclosure, the applicant finds that even though a shared service function is developed for several services to implement, a program implementation logic of the shared service function often needs to be specially designed for function codes of several specific services, which results in poor expansion performance of the shared service. If a new service is added or the functional requirements of the service are adjusted, the function code of the shared service needs to be updated to a greater extent, and often with the deepening of the service and the service function, the processing logic of the shared service is more and more complex, and the difficulty of updating and upgrading is very high.

Disclosure of Invention

The embodiment of the disclosure provides a method, a device, a platform and a medium for developing and implementing a service based on a shared service, so as to improve the expandability of the shared service and give consideration to the universality and the personalized requirements of the service.

In a first aspect, an embodiment of the present disclosure provides a shared service-based service development method, which is applied to a shared service platform, and the method includes:

acquiring attribute configuration information input by a service developer aiming at a shared service module in the development process of a target service program;

and generating a shared service code instance and a configuration file for the target business program to call according to the attribute configuration information, the code template of the shared service module and an automatic programming rule.

In a second aspect, an embodiment of the present disclosure further provides a service implementation method based on a shared service, which is applied to a shared service platform, and the method includes:

receiving a sharing service calling request sent by a service server to which a target service program belongs;

determining a sharing service code instance and a configuration file bound with the target service based on the sharing service calling request;

running the shared service code instance, taking parameters in the configuration file as input parameters, and transmitting the input parameters to the shared service code instance;

performing a data access operation on the resource object;

and feeding back the processing result of the sharing service calling request to the service server.

In a third aspect, an embodiment of the present disclosure further provides a service development device based on a shared service, configured on a shared service platform, where the device includes:

the acquisition module is used for acquiring attribute configuration information input by a service developer aiming at the shared service module in the development process of a target service program;

and the example generation module is used for generating a shared service code example and a configuration file for the target business program to call according to the attribute configuration information, the code template and the automatic programming rule of the shared service module.

In a fourth aspect, an embodiment of the present disclosure further provides a service implementation apparatus based on a shared service, configured on a shared service platform, where the apparatus includes:

the calling request receiving module is used for receiving a shared service calling request sent by a service server to which a target service program belongs;

the determining module is used for determining a shared service code instance and a configuration file bound with the target service based on the shared service calling request;

the control module is used for operating the shared service code instance, taking parameters in the configuration file as input parameters and transmitting the input parameters to the shared service code instance;

the data access module is used for executing data access operation on the resource object;

and the feedback module is used for feeding back the processing result of the shared service calling request to the service server.

In a fifth aspect, an embodiment of the present disclosure further provides a shared service platform, including:

one or more processing devices;

storage means for storing one or more programs;

when the one or more programs are executed by the one or more processing devices, the one or more processing devices implement the method for developing a service based on a shared service provided in the first aspect of the embodiment of the present disclosure or the method for implementing a service based on a shared service provided in the second aspect of the embodiment of the present disclosure.

In a sixth aspect, an embodiment of the present disclosure further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processing device, implements the method for developing a service based on a shared service provided in the first aspect of the present disclosure or the method for implementing a service based on a shared service provided in the second aspect of the present disclosure.

The embodiment of the disclosure provides a service development and realization method based on shared service, which comprises the following steps: acquiring attribute configuration information input by a service developer aiming at a shared service module in the development process of a target service program; and generating a shared service code instance and a configuration file for the target business program to call according to the attribute configuration information, the code template of the shared service module and an automatic programming rule. According to the technical scheme of the embodiment of the disclosure, the shared service code instance and the configuration file are generated, so that the workload of repeated development of the common service function by different service developers can be reduced, the expandability of the shared service is improved, and the universality and the individual service requirements of the shared service function can be considered at the same time.

The foregoing disclosure is only an overview of the technical solutions of the present disclosure, and the embodiments of the present disclosure are described below in order to make the technical means of the present disclosure more clearly understood and to make the above and other objects, features, and advantages of the present disclosure more clearly understandable.

Drawings

Other features, objects, and advantages of the disclosure will become apparent from a reading of the following detailed description of non-limiting embodiments which proceeds with reference to the accompanying drawings. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the disclosure. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:

fig. 1 is a flowchart illustrating a method for shared service based business development provided in an embodiment of the present disclosure;

FIG. 2 is a flow chart illustrating another method for shared service based business development provided in an embodiment of the present disclosure;

fig. 3 is a flowchart illustrating a method for implementing a service based on a shared service according to an embodiment of the present disclosure;

fig. 4 is a schematic structural diagram illustrating a shared service-based business development apparatus provided in an embodiment of the present disclosure;

fig. 5 is a schematic structural diagram illustrating a service implementation apparatus based on a shared service provided in an embodiment of the present disclosure;

fig. 6 shows a schematic structural diagram of a shared service platform provided in an embodiment of the present disclosure.

Detailed Description

The present disclosure is described in further detail below with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the disclosure and are not limiting of the disclosure. It should be further noted that, for the convenience of description, only some of the structures relevant to the present disclosure are shown in the drawings, not all of them.

Before discussing exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart may describe the operations (or steps) as a sequential process, many of the operations (or steps) can be performed in parallel, concurrently or simultaneously. In addition, the order of the operations may be re-arranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figure. The processes may correspond to methods, functions, procedures, subroutines, and the like.

Fig. 1 shows a flowchart of a shared service-based business development method provided in an embodiment of the present disclosure. The embodiment can be applied to the condition that a business developer carries out business development based on the shared service module of the shared service platform. The method can be executed by a service development device based on shared services, the device can be realized in a software and/or hardware mode, and the device can be configured in a shared service platform with a network communication function. As shown in fig. 1, a method for developing a service based on a shared service provided in an embodiment of the present disclosure may include:

s101, acquiring attribute configuration information input by a service developer aiming at a shared service module in the development process of a target service program.

In this embodiment, at least one shared service module is configured on the shared service platform, and each shared service module on the shared service platform can provide personalized attribute configuration. When a service developer develops a target service program, personalized attribute configuration information can be input into a shared service module called by the target service program, so that personalized configuration of functions of the shared service module is realized. In addition, an attribute configuration interface can be arranged on the shared service platform, and a service developer can configure personalized attribute configuration information for the shared service module through the attribute configuration interface.

In this embodiment, the shared service platform may obtain attribute configuration information input by the service developer for the shared service module called by the target service program in the process of developing the target service program. In the above technical solution, the advantage of obtaining the attribute configuration information input by the shared service module in the development process of the target business program is that the shared service developer can be helped to manage the personalized attribute configuration information of the own service, the business developer can be helped to manage the personalized attribute configuration information set by the business developer, and different personalized attribute requirement information can be provided for different target business programs according to the type of the target business program.

In an optional manner of this embodiment, at least one shared service module may be configured on the shared service platform. The shared service module can be a relationship service module, a wallet service module or a room service module. It can be understood that, for different shared service modules, the functions of the shared service modules and the shared service modules allow the input attribute configuration information to have certain differences.

In this embodiment, when the shared service module is a relational service module, the function of the relational service module is configured to: a relationship service may be used to establish the interrelationships between users. The interrelationship between users may include, but is not limited to, inter-concern relationships between users, fan relationships, and the like. Management data of the interrelationships between users can be processed by the relational service. For example, the relationship service can add, delete, modify, query and the like to the mutual concern relationship between users; or, the number of fans of the user can be counted through the relationship service. Optionally, when the correlation between the users is a mutual concern relationship, the attribute configuration information allowed to be input by the relationship service module may include: at least one of an upper limit number of people concerned or whether to start an application concerned. Whether to start the attention application may refer to whether to apply to the user who is concerned when the user is concerned, and the user who is concerned may be allowed to pay attention only after the user who is concerned agrees.

In this embodiment, when the shared service module is a wallet service module, the function of the wallet service module is configured to: the wallet service may be used to handle transfer operations and balance management for users based on third party payment platforms. The attribute configuration information that the wallet service module allows to input may include: at least one of the accessible third party payment platform name, the service level key which the third party payment platform allows the service party to access, and the recharge notification function. The name of the accessible third party payment platform can be configured to set which third party payment platforms are allowed to be accessed in the process of using the wallet service; the service level key which allows the service party to access by configuring the third-party payment platform can be set as a service key required when the third-party payment platform is accessed to perform service access in the process of using wallet service; whether the notification function is required in the course of using the wallet service can be set by configuring the recharge notification function.

In this embodiment, when the shared service module is a room service module, the room service module is configured to: the room service may be used to manage the relationship between the user and the room object. The room object can be managed through the room service, and the user can enter and exit the room. The attribute configuration information that the room service module allows to input may include: the user simultaneously enters at least one of an upper limit value of rooms, the maximum number of simultaneously online rooms, and the detection time of the room abnormality.

In an optional manner of this embodiment, the shared service platform may configure at least one shared service module, and the shared service module may provide one or more functional interfaces.

In this embodiment, the functional interfaces provided by the shared service module can be exposed to the service developer in the form of interface protocol specification, so that the service developer can select which interface functions of the shared service module to call based on the functions to which each functional interface belongs. Illustratively, taking the sharing service module as the relationship service module as an example, the relationship service module may provide a functional interface for the mutual concern relationship between users and a functional interface for counting the number of fans. The service developer can configure the functions used by the shared service module by selecting the functional interface, for example, the function of determining the mutual concern relationship between the users using the shared service module by selecting the functional interface of the mutual concern relationship between the users, or the function of determining the fan number statistics using the shared service module by selecting the functional interface of the fan number statistics.

And S102, generating a shared service code instance and a configuration file for calling the target business program according to the attribute configuration information, the code template of the shared service module and the automatic programming rule.

In this embodiment, the shared service module may include a code template, such as a universal code template of a service to which the shared service module belongs. Automatic programming rules, which may be understood as code generation tools, may also be included in the shared services module. The automatic programming rule may refer to a rule for parsing attribute configuration information input by a service developer and guiding how to generate code based on the attribute configuration information. The shared service platform can acquire attribute configuration information input by a service developer aiming at the shared service module in the development process of a target service program. The shared service code instance may include a large number of shared codes and a small number of business personality customization codes. The shared code may be the same code that the respective shared service code instances have had before a commonality. The generation of the personalized custom code is related to the personalized attribute configuration information input by the service developer.

In this embodiment, the shared service platform may further generate, according to the acquired attribute configuration information, a shared service code instance and a configuration file for the target business program to call, based on the code template of the shared service module and under the guidance of the automatic programming rule. By adopting the technical scheme, a service developer can meet different personalized requirements by inputting different attribute configuration information, the service developer does not need to pay attention to the shared code of the shared service and only needs to pay attention to the configuration value in the attribute configuration information, and after the attribute configuration information is input, different shared service code instances and configuration files can be generated according to the input different attribute configuration information, so that different logic services can be executed.

In an optional manner of this embodiment, generating a shared service code instance and a configuration file for being called by the target business program according to the attribute configuration information, and the code template and the automatic programming rule of the shared service module may include:

and according to the variable parameters and the functional parameters in the attribute configuration information, selecting corresponding functional functions from a code template of the shared service module, determining the calling relationship among the functional functions and the input variables of the functional functions, and generating a shared service code instance for calling the target service program.

In this embodiment, the attribute configuration information may include two types of parameter information, including a variable parameter and a function parameter. The variable parameters may be variables used during implementation of the shared service code, such as global variables and local variables. The variable parameters exist in the form of variable values in the implementation process of the shared service code, and it can be seen that the variable parameters are always the parameter contents of the variable parameters in the whole implementation process of the shared service code.

In this embodiment, for another attribute configuration information, the functional parameters may be used to guide how the code is generated, rather than using the parameter content itself. The corresponding function can be selected from the code template of the shared service module through the function parameter. For example, taking the charge notification function included in the wallet service module that allows the attribute configuration information to be input as an example, the setting of the charge notification function in the attribute configuration information as a parameter value representing "yes" or "no" may be different in the implementation process of the shared service code. The method specifically comprises the following steps: representing the parameter value of 'yes' in the attribute configuration information, and representing that a function in charge of recharging notification reminding is loaded in the implementation process of the shared service code; and the parameter value representing 'no' in the attribute configuration information indicates that the function responsible for the recharge notification reminding is not loaded in the implementation process of the shared service code. It can be seen that the "yes" or "no" executed by the function of the recharge notification reminder is not a variable in the shared service code implementation process, but is an indication of how to encode in the shared service code implementation process.

In this embodiment, a function corresponding to a function parameter may be selected from the code template through the function, and it may be determined whether to call the function corresponding to the function parameter. Further, after determining a plurality of function functions, it is also necessary to determine call relationships between the function functions. For example, taking a function of allowing the attribute configuration information to be input in the relationship service module to open the attention application as an example, first, inquiring whether the user who is concerned agrees to be concerned, and this needs to call a function to implement; and another function implementation can be called to determine whether the concerned user agrees to be concerned or not. The call relation between the function functions may include a sequential call relation between the function functions, and may also include a nested call relation between the function functions, for example, during the execution of one function, another function needs to be executed inside the function. It is to be understood that the implementation of the function functions and the call relationship between the function functions mentioned in the present embodiment are only an example.

In this embodiment, the input variables of the function may be determined by variable parameters. After obtaining the variable parameters and the functional parameters in the attribute configuration information, the shared service platform may select corresponding functional functions from the code template of the shared service module according to the variable parameters and the functional parameters, determine the call relationship between the functional functions, and input variables of the functional functions, and generate a shared service code instance and a configuration file for a target service program to call in combination with an automatic programming rule in the shared service module. The configuration file can store information such as input variables, service identifiers and the like of the function.

In general, the generated shared service code instance and configuration file for the target business program to call can be saved on a shared service platform or other platforms supporting the shared service code instance to call.

In this embodiment, after generating the shared service code instance and the configuration file for the target business program to call, the shared service platform may further save the generated shared service code instance and the configuration file for the target business program to call, so that the shared service code instance and the configuration file that have been saved may be directly called in the process of executing the business program.

In this embodiment, optionally, the shared service platform may directly store the generated shared service code instance and the configuration file on the shared service platform. Optionally, the shared service platform may further store the generated shared service code instance and the configuration file in another shared service cluster, and support the call of the shared service code instance and the configuration file through the other shared service cluster. It will be appreciated that the shared service code instances and configuration files generated by the shared service platform are not typically stored at the business developer.

The embodiment of the disclosure provides a service development method based on shared service, which comprises the steps of acquiring attribute configuration information input by a shared service module in the development process of a target service program by a service developer; and generating a shared service code instance and a configuration file for the target business program to call according to the attribute configuration information, the code template of the shared service module and the automatic programming rule. According to the technical scheme of the embodiment of the disclosure, the workload of repeated development of the common service function by different service developers can be reduced by generating the shared service code instance and the configuration file, the expandability of the shared service is improved, and meanwhile, the universality of the shared service function and the individual service requirements can be considered.

Fig. 2 is a flowchart illustrating another shared service-based service development method provided in the embodiment of the present disclosure, which is further optimized based on the above embodiment, and the embodiment of the present disclosure may be combined with various alternatives in one or more of the embodiments. As shown in fig. 2, the method for developing a service based on a shared service provided in the embodiment of the present disclosure may include:

s201, acquiring attribute configuration information and resource configuration information input by a service developer aiming at a shared service module in the development process of a target service program.

In this embodiment, at least one shared service module is configured on the shared service platform, and a service developer can input personalized attribute configuration information for the shared service module and also input resource configuration information for the shared service module in a development process of a target service program, so as to implement resource configuration of functions of the shared service module. In addition, a resource configuration interface can be arranged on the shared service platform, and a service developer can configure resource configuration information for the shared service module through the resource configuration interface.

In this embodiment, by adopting the above manner, not only can the shared service developer be helped to manage the attribute configuration information and the resource configuration information of the personalized configuration of the own service, but also the service developer can be helped to manage the attribute configuration information and the resource configuration information set by the service developer, and different personalized attribute configuration information and resource configuration information can be provided for different target service programs according to the types of the target service programs to perform service development, thereby considering the universality of the shared service function and the requirements of service individuality.

In this embodiment, the function of the shared service module and the attribute configuration information allowing the input configuration include at least one of:

when the sharing service module is a relation service module, the relation service is used for establishing the mutual relation between users and processing the management data of the relation; when the correlation is the attention correlation, the attribute configuration information includes: the upper limit number of the concerned people or whether to start the concerned application;

when the sharing service module is a wallet service module, the wallet service is used for processing transfer operation and balance management of a user based on a third-party payment platform; the attribute configuration parameters include: the accessible third party payment platform name, the service level key which the third party payment platform allows the service party to access, and the recharge notification function;

when the shared service module is a room service module, the room service is used for managing the relationship between the user and the room object; the attribute configuration parameters include: the upper limit value of the rooms simultaneously entered by the user, the maximum number of the rooms simultaneously on line and the detection time of the abnormal rooms.

S202, generating a sharing service code instance and a configuration file for calling the target business program according to the attribute configuration information, the code template of the sharing service module and the automatic programming rule.

In this embodiment, generating a shared service code instance and a configuration file for a target business program to call according to the attribute configuration information, and the code template and the automatic programming rule of the shared service module may include: and according to the variable parameters and the functional parameters in the attribute configuration information, selecting corresponding functional functions from a code template of the shared service module, determining the calling relationship among the functional functions and the input variables of the functional functions, and generating a shared service code instance and a configuration file for calling the target service program.

S203, in the process of generating the shared service code instance, generating a data access code for the resource object according to the resource configuration information, wherein the data access code is used as the data access code in the shared service code instance.

In this embodiment, the shared service platform may obtain not only the attribute configuration information input for the shared service module, but also the resource configuration information input for the shared service module. Because access to resource data needs to be executed in the process of generating and running the shared service code instance, in the process of generating the shared service code instance, the shared service platform also needs to configure a resource object according to resource configuration information input by a service developer, and generates a data access code for the resource object, which is used as a data access code in the shared service code instance, so that the generated shared service code instance can access the resource object according to the data access code. The data access code can be specifically combined to a position where the shared service code instance needs to process data, so that the shared service code instance can call the database when running.

In an optional manner of this embodiment, in the process of generating the shared service code instance, generating a data access code to the resource object according to the resource configuration information, as the data access code in the shared service code instance, may include:

and in the process of generating the shared service code instance, generating the data access code in the shared service code instance according to at least one selected database system in the resource configuration information, the constraint condition of the database system for processing data, the optional configuration parameters of each database system and the accessible storage space range of the database system.

In this embodiment, the resource configuration information that can be configured by the service developer may include: the method includes the steps of selecting at least one database system, selecting constraints on the data that the database systems need to process, selecting optional configuration parameters for each database system, and selecting a range of accessible storage space for the database systems. For example, the resource configuration information can be used by the service developer to select which data storage algorithms, databases, quantities, and coordination relationships to use, such as what tables of one mysql, two redis, one nsq, and what structure the service needs.

In this embodiment, the database system in this embodiment can be understood as various systems that can handle storage spaces of a disk and a memory and provide an interface for a data access function in the storage space. Data operations such as reading, writing, changing, deleting and the like can be carried out aiming at the data storage space in the database system. The database system may include: at least one of mysql, redis, ESPLUS, and nsq.

In this embodiment, the optional configuration parameters of each database system can be understood as a selection of which data types can be supported by each database system and the supported data types. The constraint condition that the database system needs to process data can be understood that each database system can only process respectively appointed data when processing data, for example, in a relational service, data of a certain type of users can only be processed by a mysql database, and relational data can only be processed by a redis database.

In this embodiment, the accessible storage space range may refer to a physical storage space range. A service developer can perform static or dynamic allocation on the accessible storage space range of the database system by setting parameters in the resource configuration information, so as to realize whether the storage resources of each service are independent; or, a plurality of services share the storage resource. For example, if the mysql database belongs to one independent server and the redis database belongs to another independent server, it can be predetermined that the mysql database and the redis database are independent from each other.

In the embodiment, in the process of generating the shared service code instance, the data access code in the shared service code instance is generated according to at least one of the database systems selected from the resource configuration information, the constraint condition of the database systems for processing data, the optional configuration parameter of each database system, and the accessible storage space range of the database system. The data access code may be specifically combined to a location in each function where data needs to be processed, so that the function calls the database according to the data access code.

In an optional manner of this embodiment, at least two shared service modules may be provided on the shared service platform.

In this embodiment, the shared service platform may be provided with at least two shared service modules, and each shared service module operates independently. If the target business program needs to sequentially call more than two shared service modules, the business developer can be set to sequentially call a plurality of shared service modules instead of sequentially calling between the shared service modules. By adopting the setting mode, the universality of the shared service can be stronger. In addition, optionally, the accessible storage space ranges in the resource configuration information of different shared service modules may be independent of each other.

The technical scheme of the embodiment of the disclosure not only can reduce the workload of repeated development of the common service function by different service developers, improve the expandability of the shared service, but also can consider the universality and the individual service requirements of the shared service function; in addition, in the process of generating the shared service code instance, the service developer already configures the logic resource through the resource configuration information, so that the developer does not need to pay attention to the actual physical resource of each access party, and when the shared service platform receives the shared service call request, the logic resource requirement can be mapped to the physical resource for processing according to the configured resource configuration information.

Fig. 3 shows a flowchart of a service implementation method based on a shared service provided in an embodiment of the present disclosure. The embodiment of the disclosure is applicable to the situation that a service developer performs service implementation based on the shared service of the shared service platform. The method can be executed by a service implementation device based on shared services, the device can be implemented in a software and/or hardware manner, and the device can be configured in a shared service platform with network communication function. As shown in fig. 3, the method for implementing a service based on a shared service provided in the embodiment of the present disclosure may include:

s301, receiving a sharing service calling request sent by a service server to which a target service program belongs.

In this embodiment, after the shared service platform generates the shared service code instance and the configuration file for the target business program to call, the shared service code instance and the configuration file are stored, so as to perform subsequent shared service call. When the business server to which the target business program belongs needs to call the shared service, the business server may send a shared service call request to the shared service platform. The shared service platform can receive a shared service call request sent by a service server to which the target service program belongs. The shared service call request may be a request generated by triggering when a service implementer of the service server needs to call to perform sharing of the service code instance and the configuration file.

S302, determining a sharing service code instance and a configuration file bound with the target service based on the sharing service calling request.

In this embodiment, when saving the shared service code instance and the configuration file for the target business program to call, the shared service platform may bind the target business program with the generated shared service code instance and configuration file. The shared service platform can respond to the received shared service calling request and determine a shared service code instance and a configuration file bound with the target service.

In an optional manner of this embodiment, determining, based on the shared service invocation request, the shared service code instance and the configuration file bound to the target service may include:

receiving a sharing service calling request through an application program frame code of a sharing service platform, and extracting a target service identifier from the sharing service calling request;

and inquiring and acquiring the bound shared service code instance and the configuration file according to the target service identifier.

In this embodiment, the application framework code of the shared service platform is allowed to be used in each service, and the shared service platform may receive a shared service invocation request through the application framework code of the shared service platform, and extract the carried target service identifier from the shared service invocation request. The sharing service platform can acquire the sharing service code example bound by the target service according to the extracted target service identifier through the application program frame code, and can inquire the bound configuration file according to the target service identifier through the application program frame code. The configuration file may include input parameters of the shared service code instance configured for the target service.

In an optional manner of this embodiment, after receiving the shared service call request through the application framework code of the shared service platform, the method may further include: and authenticating the target service party according to the target service identifier through the application program frame code.

In this embodiment, the authority of the target service party can be verified according to the target service identifier through the application framework code. If the verification is passed, the bound shared service code instance can be inquired and obtained according to the target service identifier through the application program frame code; and if the verification is not passed, inquiring and acquiring the bound shared service code instance according to the target service identifier without passing through the application program framework code.

In another optional manner of this embodiment, after receiving the shared service invocation request through the application framework code of the shared service platform, the method may further include: and performing exception monitoring and log generation operation in the running process of the shared service code instance through the application program framework code. Wherein, the anomaly monitoring may include: metric monitoring and target traffic monitoring.

In yet another optional manner of this embodiment, after receiving the shared service call request through the application framework code of the shared service platform, the method may further include: and generating a virtual access entity for accessing the resource object according to the IP, the port and the password of the service server through the application program frame code.

In this embodiment, when the shared service platform obtains the IP, the port, and the password of the service server from the shared service invocation request, a virtual client and a model access entity for accessing the resource object may be generated by the application framework code according to the IP, the port, and the password of the service server.

S303, running the shared service code instance, taking the parameters in the configuration file as input parameters, and transmitting the input parameters to the shared service code instance.

In this embodiment, the shared service platform may allocate a process and a memory for the shared service code instance bound to the target service, and load the shared service code instance bound to the target service into the memory for running. The shared service platform can take the parameters in the configuration file bound with the target service as input parameters and transmit the input parameters to the shared service code instance bound with the target service so as to control the operation of the shared service code instance.

S304, executing data access operation on the resource object.

In this embodiment, the data access code may be specifically combined to a location in each functional function where data needs to be processed, and in the running process of the shared service code instance, data access operation may be performed on the resource object according to the data access code. The data access code can also comprise: and when the IP, the port and the password of the service party are acquired from the shared service calling request, generating a virtual access entity for accessing the resource object through the application program framework code, such as a virtual client and a model access entity required by the database.

S305, feeding back the processing result of the sharing service calling request to the service server.

In yet another alternative of this embodiment, at least two shared service modules may be provided on the shared service platform.

In this embodiment, at least two shared service modules are provided on the shared service platform, and each shared service module may include: various function functions and libraries can be used by the shared service module. Each shared service module may include: the automatic programming rule may guide, for example, what attribute configuration information selects what function, and determines a call relationship between function functions.

The technical scheme of the embodiment of the invention not only can reduce the workload of repeated development of the same service function by different service developers, but also realizes convenient expansion in a mode of application program frame codes, does not need to determine the corresponding relation with the service in the shared service codes, realizes shared service expansion by using a shared service code example and a configuration file in a service identification binding mode, and does not need to make excessive adjustment on a shared service module when the service is newly added, thereby improving the expandability of the shared service and considering the universality and the individual service requirements of the shared service function.

Fig. 4 is a schematic structural diagram of a shared service-based service development apparatus provided in an embodiment of the present disclosure, which is applicable to a situation where a service developer performs service development based on a shared service of a shared service platform. The device can be implemented in software and/or hardware, and can be configured in a shared service platform with a network communication function.

As shown in fig. 4, the service development device based on shared service provided in the embodiment of the present disclosure may include: an acquisition module 401 and an instance generation module 402. Wherein:

an obtaining module 401, configured to obtain attribute configuration information input by a service developer for a shared service module in a process of developing a target service program;

an instance generating module 402, configured to generate a shared service code instance and a configuration file for the target service program to call according to the attribute configuration information, and the code template and the automatic programming rule of the shared service module.

On the basis of the foregoing embodiment, optionally, the instance generating module 402 may include:

and the code example generating unit is used for selecting corresponding function functions from the code template of the shared service module according to the variable parameters and the function parameters in the attribute configuration information, determining the calling relationship among the function functions and the input variables of the function functions, and generating the shared service code example for the target business program to call.

On the basis of the foregoing embodiment, optionally, the shared service platform is configured with at least one shared service module, where the function of the shared service module and the attribute configuration information allowing input configuration include at least one of:

the sharing service module is a relation service module, and the relation service is used for establishing the mutual relation among users and processing the management data of the relation; when the correlation is a concern relationship, the attribute configuration information includes: the upper limit number of the concerned people or whether to start the concerned application;

the sharing service module is a wallet service module, and the wallet service is used for processing transfer operation and balance management of a user based on a third-party payment platform; the attribute configuration parameters include: the accessible third party payment platform name, the service level key which the third party payment platform allows the service party to access, and the recharge notification function;

the shared service module is a room service module, and the room service is used for managing the relationship between the user and the room object; the attribute configuration parameters include: the upper limit value of the rooms simultaneously entered by the user, the maximum number of the rooms simultaneously on line and the detection time of the abnormal rooms.

On the basis of the foregoing embodiment, optionally, the obtaining module 401 may be further configured to obtain resource configuration information input by a service developer for a shared service module in a process of developing a target service program;

accordingly, the apparatus may further include: an access code generating module 403, configured to generate a data access code for the resource object according to the resource configuration information in the process of generating the shared service code instance, as the data access code in the shared service code instance.

On the basis of the above embodiment, optionally, the access code generating module 403 may include:

and the data access code generating unit is used for generating the data access codes in the shared service code examples according to at least one selected database system in the resource configuration information, the constraint condition of the database system for processing data, the optional configuration parameters of each database system and the accessible storage space range of the database system in the generation process of the shared service code examples.

On the basis of the foregoing embodiment, optionally, the database system may include at least one of: mysql, redis, ESPLUS, and nsq.

On the basis of the above embodiment, optionally, the shared service platform may be provided with at least two shared service modules.

On the basis of the above embodiment, optionally, the accessible storage space ranges in the resource configuration information of different shared service modules may be independent of each other.

The service development device based on the shared service provided in the embodiment of the present disclosure may execute the service development method based on the shared service provided in any embodiment of the present disclosure, and has the corresponding functions and beneficial effects for executing the service development method based on the shared service.

Fig. 5 is a schematic structural diagram illustrating a shared service-based service implementation apparatus provided in an embodiment of the present disclosure, which is applicable to a case where a service developer implements a service based on a shared service of a shared service platform. The device can be implemented in software and/or hardware, and can be configured in a shared service platform with a network communication function. As shown in fig. 5, the service implementation apparatus based on a shared service provided in the embodiment of the present disclosure may include: a call request receiving module 501, a determining module 502, a control module 503, a data access module 504 and a feedback module 505. Wherein:

a calling request receiving module 501, configured to receive a shared service calling request sent by a service server to which a target service program belongs;

a determining module 502, configured to determine, based on the shared service call request, a shared service code instance and a configuration file bound to the target service;

a control module 503, configured to run the shared service code instance, and transmit parameters in the configuration file as input parameters to the shared service code instance;

a data access module 504, configured to perform a data access operation on the resource object;

and a feedback module 505, configured to feed back a processing result of the shared service invocation request to the service server.

On the basis of the foregoing embodiment, optionally, the determining module 502 may include:

the identification extraction unit is used for receiving a sharing service calling request through an application program framework code of a sharing service platform and extracting a target service identification from the sharing service calling request;

and the query unit is used for querying and acquiring the bound shared service code instance and the configuration file according to the target service identifier.

On the basis of the above embodiment, optionally, the apparatus may further include at least one of the following:

an authentication module 506, configured to authenticate a target service party according to the target service identifier through the application framework code;

an exception monitoring log generation module 507, configured to perform exception monitoring and log generation operations in the running process of the shared service code instance through the application framework code;

an access entity generating module 508, configured to generate, according to the IP, the port, and the password of the service server, a virtual access entity for accessing the resource object through the application framework code.

On the basis of the above embodiments, optionally, at least two shared service modules may be provided on the shared service platform.

The service implementation device based on the shared service provided in the embodiment of the present disclosure may execute the service implementation method based on the shared service provided in any embodiment of the present disclosure, and has corresponding functions and beneficial effects for executing the service implementation method based on the shared service.

Fig. 6 shows a schematic structural diagram of a shared service platform provided in an embodiment of the present disclosure. Referring to FIG. 6, a schematic structural diagram of a shared services platform (e.g., server) 600 suitable for use in implementing embodiments of the present disclosure is shown. The shared services platform shown in fig. 6 is only an example, and should not bring any limitations to the function and scope of use of the disclosed embodiments.

As shown in fig. 6, shared services platform 600 may include a processing device (e.g., central processing unit, graphics processor, etc.) 601 that may perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)602 or a program loaded from a storage device 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data necessary for the operation of the shared service platform 600 are also stored. The processing device 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.

Generally, the following devices may be connected to the I/O interface 605: input devices 606 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 607 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 608 including, for example, tape, hard disk, etc.; and a communication device 609. The communication means 609 may allow the shared service platform 600 to communicate with other devices wirelessly or by wire to exchange data. While FIG. 6 illustrates a shared services platform 600 having various devices, it is to be understood that not all illustrated devices are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided.

In particular, according to a shared service based business development method provided in the foregoing embodiments of the present disclosure, the process of shared service based business development described above with reference to the flowchart may be implemented as a computer software program. For example, embodiments of the present disclosure may include a computer program product comprising a computer program embodied on a computer readable medium, the computer program containing program code for performing the shared service based business development method illustrated in the flowchart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication means 609, or may be installed from the storage means 608, or may be installed from the ROM 602. When executed by the processing device 601, the computer program performs the above-described functions defined in the technical solutions of the shared service based service development methods provided in the foregoing embodiments of the present disclosure.

In particular, according to a method for implementing a shared service based service provided in the foregoing embodiments of the present disclosure, the processes of implementing a shared service based service described above with reference to the flowcharts may also be implemented as a computer software program. For example, embodiments of the present disclosure may also include a computer program product comprising a computer program embodied on a computer-readable medium, the computer program containing program code for performing the shared service based business implementation method illustrated in the flowchart. Referring to fig. 6, in such an embodiment, the computer program may also be downloaded and installed from a network through the communication means 609, or installed from the storage means 608, or installed from the ROM 602. When executed by the processing device 601, the computer program performs the above functions defined in the technical solutions of the service implementation method based on shared services provided in the foregoing embodiments of the present disclosure.

It should be noted that the computer readable medium in the present disclosure can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.

The computer readable medium may be embodied in the shared services platform; or may exist separately without being assembled into the shared service platform.

Optionally, the computer readable medium carries one or more programs, which when executed by the shared service platform, cause the shared service platform to: acquiring attribute configuration information input by a service developer aiming at a shared service module in the development process of a target service program; and generating a shared service code instance and a configuration file for the target business program to call according to the attribute configuration information, and a code template and an automatic programming rule of the shared service module.

Optionally, the computer readable medium carries one or more programs, which when executed by the shared service platform, further cause the shared service platform to: receiving a sharing service calling request sent by a service server to which a target service program belongs; determining a sharing service code instance and a configuration file bound with the target service based on the sharing service calling request; running the shared service code instance, taking parameters in the configuration file as input parameters, and transmitting the input parameters to the shared service code instance; performing a data access operation on the resource object; and feeding back the processing result of the sharing service calling request to the service server.

Computer program code for carrying out operations for aspects of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units described in the embodiments of the present disclosure may be implemented by software or hardware. Where the name of a unit does not in some cases constitute a limitation of the unit itself, for example, the first retrieving unit may also be described as a "unit for retrieving at least two internet protocol addresses".

The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the disclosure herein is not limited to the particular combination of features described above, but also encompasses other embodiments in which any combination of the features described above or their equivalents does not depart from the spirit of the disclosure. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.

Claims

1. A business development method based on shared service is characterized in that the method is applied to a shared service platform, and the method comprises the following steps:

generating a sharing service code instance and a configuration file for the target business program to call according to the attribute configuration information, the code template of the sharing service module and an automatic programming rule;

the shared service platform is provided with at least two shared service modules, and the shared service modules operate independently;

the accessible storage space ranges in the resource configuration information of different shared service modules are independent of each other.

2. The method of claim 1, wherein generating a shared service code instance and configuration file for the target business program to call according to the attribute configuration information, and a code template and an automatic programming rule of the shared service module comprises:

and according to the variable parameters and the functional parameters in the attribute configuration information, selecting corresponding functional functions from the code template of the shared service module, determining the calling relationship among the functional functions and the input variables of the functional functions, and generating a shared service code instance for the target service program to call.

3. The method according to claim 1 or 2, wherein the shared service platform is configured with at least one shared service module, wherein the function of the shared service module and the attribute configuration information allowing the configuration to be input comprise at least one of:

the sharing service module is a wallet service module, and the wallet service is used for processing transfer operation and balance management of a user based on a third-party payment platform; the attribute configuration information allowed to be input by the wallet service module includes: the accessible third party payment platform name, the service level key which the third party payment platform allows the service party to access, and the recharge notification function;

the shared service module is a room service module, and the room service is used for managing the relationship between the user and the room object; the attribute configuration information that the room service module allows to input includes: the upper limit value of the rooms simultaneously entered by the user, the maximum number of the rooms simultaneously on line and the detection time of the abnormal rooms.

4. The method of any of claims 1-2, further comprising:

acquiring resource configuration information input by a service developer aiming at a shared service module in the development process of a target service program;

and in the process of generating the shared service code instance, generating a data access code for the resource object according to the resource configuration information, wherein the data access code is used as the data access code in the shared service code instance.

5. The method of claim 4, wherein during the generation of the shared service code instance, generating a data access code for a resource object according to resource configuration information, and wherein the generating of the data access code for the shared service code instance comprises:

and in the process of generating the shared service code instance, generating a data access code in the shared service code instance according to at least one selected database system in the resource configuration information, a constraint condition of the database system for processing data, an optional configuration parameter of each database system and at least one of an accessible storage space range of the database system.

6. The method of claim 5, wherein the database system comprises at least one of: mysql, redis, ESPLUS, and nsq.

7. The method of claim 1, wherein the accessible storage space ranges in the resource configuration information of different shared service modules are independent of each other.

8. A service implementation method based on shared service is characterized in that the method is applied to a shared service platform, and the method comprises the following steps:

performing a data access operation on the resource object;

9. The method of claim 8, wherein determining the shared service code instance and the configuration file bound to the target service based on the shared service invocation request comprises:

and inquiring and acquiring the bound shared service code instance and configuration file according to the target service identifier.

10. The method of claim 9, wherein after receiving the shared service invocation request, further comprising at least one of:

authenticating a target service party according to the target service identifier through the application program frame code;

performing exception monitoring and log generation operation in the running process of the shared service code instance through the application program frame code;

and generating a virtual access entity for accessing the resource object according to the IP, the port and the password of the service server through the application program frame code.

11. The method of claim 8, wherein at least two shared service modules are provided on a shared service platform.

12. A service development device based on shared service, configured on a shared service platform, the device comprising:

the instance generation module is used for generating a shared service code instance and a configuration file for the target business program to call according to the attribute configuration information, the code template and the automatic programming rule of the shared service module;

13. The apparatus of claim 12, wherein:

the acquisition module is also used for acquiring resource configuration information input by a service developer aiming at the shared service module in the development process of a target service program;

the device further comprises: and the access code generation module is used for generating a data access code for the resource object according to the resource configuration information in the shared service code generation process, and the data access code is used as the data access code in the shared service code instance.

14. A service implementation apparatus based on shared service, configured on a shared service platform, the apparatus comprising:

15. A shared services platform, comprising:

one or more processing devices;

storage means for storing one or more programs;

when executed by the one or more processing devices, cause the one or more processing devices to implement the shared service based business development method of any one of claims 1-7 or the shared service based business implementation method of any one of claims 8-11.

16. A computer-readable storage medium on which a computer program is stored, the program, when executed by a processing device, implementing the shared service based business development method of any one of claims 1 to 7 or the shared service based business implementation method of any one of claims 8 to 11.