WO2019221234A1

WO2019221234A1 - Conversion logic generation device, http method execution system, http method execution method, and conversion logic generation program

Info

Publication number: WO2019221234A1
Application number: PCT/JP2019/019511
Authority: WO
Inventors: 好彦伊藤
Original assignee: 日本電信電話株式会社
Priority date: 2018-05-18
Filing date: 2019-05-16
Publication date: 2019-11-21
Also published as: JP2019200691A

Abstract

Provided is a conversion logic generation device 1 comprising: a storage device 10 for storing selection logic data 12 in which a process classification indicating whether to carry out a command with respect to a database table with a synchronous process or an asynchronous process is associated with a condition for applying the process classification; and a conversion logic generation part 22 for referring to the selection logic data 12, identifying the table, command, and process classification which meet the condition, and outputting conversion logic data L in which an HTTP method corresponding to the identified command and a subject for processing by the HTTP method corresponding to the identified table are associated with the process classification of the identified command.

Description

Conversion logic generation device, HTTP method execution system, HTTP method execution method, and conversion logic generation program

The present invention relates to a conversion logic generation device, an HTTP method execution system, an HTTP method execution method, and a conversion logic generation program that generate conversion logic data for converting an HTTP method received from an application execution device into a database command.

In recent years, APIs (Applications Programming Interfaces) have been converted into APIs (Applications Programming Interfaces) to use various resources of the company or its own organization over the network, and partnerships have been facilitated by external provision of APIs, and in-house development has become more efficient. . Here, the API conforms to REST (REpresentational State Transfer).

The REST API uses HTTP (Hypertext Transfer Protocol), and each CRUD operation (C: Create, R: Read, U: Update, D: for a resource uniquely represented by a URI (Uniform Resource Identifier)) Delete) corresponds to HTTP POST / GET / PUT (PATCH) / DELETE. In addition, as a resource representation of the REST API, a data format having a high affinity with web technologies such as JSON (JavaScript (registered trademark) Object Notation) and XML (Extensible Markup Language) is used. Currently, many APIs are provided in the REST API.

When creating an API for manipulating data managed by the database management system (DBM), (1) conversion of HTTP method and command for manipulating DBM data, (2) URI and DBM table specified by HTTP or View conversion, (3) Conversion of parameters specified by HTTP and DBM attributes, and (4) Determination of processing type for synchronous processing or asynchronous processing must be performed.

Here, there is a method for operating the data managed by the DBM using an API. For example, the method described in Patent Document 1 converts a sequence and a REST including a protocol included in the DBM. However, Patent Document 1 must use the API after knowing the correspondence between DBM and REST, and even web engineers who only want to use the DBM from the API have knowledge and know-how about the specifications of the DBM. It may be necessary to grasp and raise the barrier of API utilization.

In view of such a situation, there are tools that replace operations on DBM with HTTP methods and the like (Non-Patent Document 1 and Non-Patent Document 2). This tool converts a CRUD operation on the DBM into each HTTP method of REST, converts each table and view of the DBM into a URI, and converts a DBM record and attribute into a JSON or XML expression. With this tool, if there is a DB managed by an existing DBM, it can be provided as an API without any special development, so web engineers can manage it without any special DBM knowledge or know-how. Data can be used.

Japanese Patent No. 6169622

However, none of the methods described in Patent Document 1 and

Non-Patent Documents

1 and 2 describe a method for determining a processing type to be performed by synchronous processing or asynchronous processing.

When generating an API, it is necessary to specify a processing type indicating either synchronous processing or asynchronous processing. However, since none of the prior art documents touch this point, an API developer or the like designates it. There is a need. However, in order to specify the processing type, it is necessary to grasp the data structure and processing time in the DBM, and API developers who are not familiar with the DBM mechanism may not be able to set the processing type appropriately.

Therefore, an object of the present invention is to provide a conversion logic generation device, an HTTP method execution system, an HTTP method execution method, and a conversion logic generation program that can optimally select synchronous processing or asynchronous processing when creating an API from an HTTP method. That is.

In order to solve the above-described problem, a first feature of the present invention relates to a conversion logic generation apparatus that generates conversion logic data for converting an HTTP method received from an application execution apparatus into a database command. The conversion logic generation device according to the first feature stores selection logic data in which a processing type indicating whether a command for a database table is performed in synchronous processing or asynchronous processing and a condition for applying the processing type are associated with each other A table, a command that matches the condition, and a processing type with reference to the selection logic data, an HTTP method corresponding to the specified command, a processing target of the HTTP method corresponding to the specified table, A conversion logic generation unit that outputs conversion logic data associated with the processing type of the identified command is provided.

Here, the selection logic data may be associated with an asynchronous process as a process type for a condition that takes time to execute on the table.

The selection logic data may associate asynchronous processing as a processing type with a condition involving access to other tables in the database.

The selection logic data is data in which a command to the database and a processing type of the command for the table are associated with each table of the database, and the conversion logic generation unit receives HTTP from the application execution device from the selection logic data. A processing type is specified from the command corresponding to the method and the table corresponding to the processing target of the HTTP method, and the conversion logic data in which the HTTP method, the processing target of the HTTP method, and the processing type of the specified command are associated with each other is obtained. It may be output.

The second feature of the present invention is that a conversion logic generating device for generating conversion logic data for converting an HTTP method received from an application execution device into a command of a database, and an HTTP method based on the conversion logic data are stored in the database. The present invention relates to an HTTP method execution system that includes an HTTP method execution device that converts and executes a command, and a database management device that manages a database. In the HTTP method execution system according to the second feature of the present invention, the conversion logic generation device has a processing type indicating whether a command for a database table is executed in a synchronous process or an asynchronous process, and a condition for applying the process type A storage device that stores selection logic data associated with each other, a table and a command that meet the conditions and a processing type are identified with reference to the selection logic data, an HTTP method that corresponds to the identified command, and the identified table A conversion logic generation unit that outputs conversion logic data in which the processing target of the corresponding HTTP method is associated with the processing type of the specified command is provided. The HTTP method execution device receives the HTTP method and the processing target from the application execution device. App request that receives processing request including The processing request and conversion logic data are referenced to convert the processing request into a database request for the database, and the command processing type is determined from the HTTP method included in the processing request and the processing target included in the processing request. A conversion unit and a database request processing unit that processes a database request based on the processing type determined by the conversion unit are provided.

Here, when the processing type determined by the conversion unit is synchronous processing, the database request processing unit transmits a database request to the database management device, and transmits a processing result received from the database management device to the application execution device. When the processing type determined by the conversion unit is asynchronous processing, a processing response including an inquiry URI that provides a processing result for the processing request is transmitted to the application execution device, and a database request is transmitted to the database management device, and database management is performed. An asynchronous processing unit that holds the processing result received from the device in association with the inquiry URI may be provided.

A third feature of the present invention is that a conversion logic generation device that generates conversion logic data for converting an HTTP method received from an application execution device into a database command, and an HTTP method based on the conversion logic data are stored in the database. The present invention relates to an HTTP method execution method used for an HTTP method execution system that includes an HTTP method execution device that converts and executes a command and a database management device that manages a database. The HTTP method execution method according to the third aspect of the present invention includes a process type indicating whether the conversion logic generation device performs a command for a database table in a synchronous process or an asynchronous process, and a condition for applying the process type Storing the selection logic data associated with each other, the conversion logic generation device refers to the selection logic data, identifies the table and command that match the conditions, and the processing type, and the HTTP method corresponding to the identified command; The HTTP method processing target corresponding to the specified table, the step of outputting the conversion logic data corresponding to the specified command processing type, and the HTTP method execution device from the application execution device to the HTTP method and processing target Receiving a processing request including: The TTP method execution device refers to the conversion logic data, converts the processing request into a database request for the database, and determines the processing type of the command from the HTTP method included in the processing request and the processing target included in the processing request. And an HTTP method execution device includes a step of processing a database request based on the determined processing type.

The fourth feature of the present invention relates to a conversion logic generation program for causing a computer to function as the conversion logic generation device described in the first feature of the present invention.

According to the present invention, there is provided a conversion logic generation device, an HTTP method execution system, an HTTP method execution method, and a conversion logic generation program capable of optimally selecting synchronous processing or asynchronous processing when creating an API from an HTTP method. Can do.

It is a figure explaining the system configuration | structure of the information processing system which concerns on embodiment of this invention. It is a sequence diagram explaining the HTTP method execution method which concerns on embodiment of this invention. It is a figure explaining the hardware constitutions and functional block of the conversion logic production | generation apparatus which concern on embodiment of this invention. It is a figure explaining an example of conversion logic data concerning an embodiment of the invention. It is a figure explaining the command of the database corresponding to the HTTP method designated by API, and each HTTP method. It is a flowchart explaining the process of the conversion logic production | generation means by the conversion logic production | generation part which concerns on embodiment of this invention. It is a figure explaining the hardware constitutions and functional block of the HTTP method execution apparatus which concerns on embodiment of this invention. It is a figure explaining an example of the processing result data concerning an embodiment of the invention. It is a figure explaining an example of the concrete table which a database management apparatus manages. It is a figure explaining the table structure data of the customer table shown in FIG. It is a figure explaining the table structure data of the product table shown in FIG. It is a figure explaining the table structure data of the order name list table shown in FIG.

Next, an embodiment of the present invention will be described with reference to the drawings. In the following description of the drawings, the same or similar parts are denoted by the same or similar reference numerals.

(Information processing system)
With reference to FIG. 1, an information processing system 9 in which the conversion logic generation device 1 according to the embodiment of the present invention is used will be described. The information processing system 9 includes an HTTP method execution system 5, an application development device 6, and an application execution device 7. The HTTP method execution system 5, the application development device 6, and the application execution device 7 are connected to each other via a communication network 8 such as the Internet so as to be able to communicate with each other.

The application development device 6 generates an application using the API according to the embodiment of the present invention. Further, the application development apparatus 6 registers information related to the API used in the generated application in the HTTP method execution system 5.

The application execution device 7 executes the application generated by the application development device 6, uses the API to access the HTTP method execution system 5 in the application, requests processing, and receives the processing result from the HTTP method execution system 5. .

The HTTP method execution system 5 converts the API transmitted by the application execution device 7 into a command for accessing the data managed by the database management device 3, processes the data, and transmits the processing result to the application execution device 7. .

The HTTP method execution system 5 includes a conversion logic generation device 1, an HTTP method execution device 2, and a database management device 3. The conversion logic generation device 1, the HTTP method execution device 2, and the database management device 3 are connected to each other via a communication network 4 such as a LAN (Local Area Network). In the embodiment of the present invention, the case where the conversion logic generation device 1, the HTTP method execution device 2, and the database management device 3 are separate hardware will be described. The functions of each device may be realized by three or more pieces of hardware. Each device may be a virtual machine.

The conversion logic generation device 1 generates conversion logic data L for converting the HTTP method received from the application execution device 7 into a database command. The conversion logic generation device 1 generates, based on the API-related information received from the application development device 6, the conversion logic data L converted into an HTTP method transmitted in advance by the application and a command for a database corresponding to the HTTP method.

When receiving the HTTP method processing request from the application execution device 7, the HTTP method execution device 2 accesses and processes the database with a command corresponding to the HTTP method based on the conversion logic data L, and executes the result. Transmit to device 7.

The database management device 3 is a DBM that manages data accessed by the application execution device 7. The database management device 3 holds data in the form of a plurality of tables or views, and functions as an interface for accessing the data by SQL (Structured Query) Language. The database management device 3 receives a database request (DB request) from the HTTP method execution device 2 and transmits a database response (DB response) including a processing result to the HTTP method execution device 2.

In the embodiment of the present invention, API means REST API. In the API, an HTTP method that can be converted into an SQL command, a URI that identifies a table or view of the database management apparatus 3, a parameter in JSON format or query format that can identify an attribute of the table or view, and the like are specified.

The HTTP method execution system 5 according to the embodiment of the present invention determines a processing type indicating whether the API received from the application execution device 7 is to be performed synchronously or asynchronously in accordance with the conversion logic data L created in advance. The HTTP method is executed with the determined processing type. When an application requests API processing to the HTTP method execution system 5, it is not necessary to specify the processing type of the HTTP method, and the application developer is not required to have knowledge about DBM.

(HTTP method execution method)
With reference to FIG. 2, the HTTP method execution method according to the embodiment of the present invention will be described.

In step S1, the application execution device 7 transmits a processing request to the HTTP method execution device 2. This processing request includes an HTTP method and a processing target. This processing target is information for specifying data managed by the database management device 3.

When receiving the processing request from the application execution device 7, the HTTP method execution device 2 acquires the conversion logic data L from the conversion logic generation device 1 in step S2. The HTTP method execution device 2 may acquire the conversion logic data L in advance.

In step S3, the HTTP method execution device 2 converts the processing request received from the application execution device 7 into a database request. The database request includes a database command corresponding to the HTTP method included in the processing request and a processing target for specifying data in the database corresponding to the processing target included in the processing request. In step S4, the HTTP method execution device 2 specifies the processing type of the received processing request according to the conversion logic data L, and switches the processing according to the processing type specified in step S5.

If the synchronization process is identified, the HTTP method execution device 2 transmits the database request converted in step S3 to the database management device 3 in step S11. The database management device 3 processes the database request received in step S11, and transmits a database response including the processing result to the HTTP method execution device 2 in step S12. The HTTP method execution device 2 converts the database response received in step S12 into a process response addressed to the application execution device 7. In step S <b> 13, the HTTP method execution device 2 transmits a processing response to the application execution device 7 as a response to the processing request received in step S <b> 1.

On the other hand, if the asynchronous method is specified, the HTTP method execution device 2 transmits a response in which the inquiry URI is set to the application execution device 7 as a response to the processing request received in step S1 in step S21. The inquiry URI is used for the application execution device 7 to receive a processing result for the processing request transmitted in step S1. In step S22, the HTTP method execution device 2 transmits the database request converted in step S3 to the database management device 3 in step S22. The database management device 3 processes the database request received in step S22, and transmits a database response including the processing result to the HTTP method execution device 2 in step S23. In step S24, the HTTP method execution device 2 stores the inquiry URI transmitted in step S21 and the processing result received in step S23 in association with each other.

When the application execution device 7 transmits an inquiry request specifying the inquiry URI to the HTTP method execution device 2 in step S25, the HTTP method execution device 2 displays the processing result associated with the received inquiry URI in step S26. To the application execution device 7. Although not shown, if the application execution device 7 transmits an inquiry request to the HTTP method execution device 2 before holding the processing result in step S24, the HTTP method execution device 2 indicates that the processing has not yet been completed. Return to the application execution device 7.

(Conversion logic generator)
With reference to FIG. 3, the conversion logic production | generation apparatus 1 which concerns on embodiment of this invention is demonstrated. The conversion logic generation device 1 is a general computer including a storage device 10, a processing device 20, and a communication control device 30. The functions shown in FIG. 3 are realized by a general computer executing the conversion logic generation program.

The storage device 10 is a read only memory (ROM), a random access memory (RAM), a hard disk or the like, and stores various data such as input data, output data, and intermediate data for the processing device 20 to execute processing. . The processing device 20 is a CPU (Central Processing Unit) that reads / writes data stored in the storage device 10 and inputs / outputs data to / from the communication control device 30 to perform processing in the conversion logic generation device 1. Execute. The communication control device 30 is an interface for the conversion logic generation device 1 to be communicably connected to the HTTP method execution device 2 and the database management device 3.

The storage device 10 stores table structure data 11, selection logic data 12, and conversion logic data L.

The table structure data 11 is structure data of a table managed by the database management device 3. The table structure data 11 is described in DDL (Database Definition Language). The format of the table structure data 11 is shown in, for example, each (a) of FIGS. 10 to 12, but the format shown in these drawings is not necessary.

The selection logic data 12 is data in which a process type indicating whether a command for a database table managed by the database management apparatus 3 is performed in a synchronous process or an asynchronous process and a condition for applying the process type are associated with each other. The selection logic data 12 is created in advance by an administrator of the HTTP method execution system 5 or the like.

For example, the selection logic data 12 associates “asynchronous processing” as the processing type with the condition “it takes time to execute the table”. The selection logic data 12 associates “asynchronous processing” as the processing type with the condition “with access to other tables in the database”. Further, the selection logic data 12 may associate “synchronization processing” as the default processing type for cases outside the specified conditions.

Further, the selection logic data 12 may be data in which, for each table managed by the database management device 3, a command to the database is associated with a processing type of this command for this table. In this case, the selection logic data 12 can specify the processing type for each command (INSERT, SELECT, UPDATE, and DELETE) for each table.

The conversion logic data L is data that the conversion logic generation device 1 according to the embodiment of the present invention outputs to the HTTP method execution device 2. The conversion logic data L is data in which the HTTP method received from the application execution device 7, the processing target of the HTTP method, and the processing type of the command corresponding to the HTTP method are associated with each other.

For example, as shown in FIG. 4, the conversion logic data L includes a column related to an API received from an application and a column related to SQL for processing a database. Each sub-item of the item related to API and each sub-item of the item related to SQL are associated with each other so that they can be converted to each other. The items related to the API include the URI of the processing target specified by the API and the small items of parameters for specifying the attributes in the table. The parameters include a format in which parameters included in the API are described in the JSON format and a format described in the query format. The items related to SQL include the table name corresponding to the small item of the processing target URI of the item related to API, and each small item described in the database table of the attribute specified by the parameter small item.

Further, the conversion logic data L has an HTTP method specified by the API in an item related to the API, and a database command corresponding to the HTTP method is associated in the item related to the SQL. As shown in FIG. 5, the relationship between the HTTP method specified by the API and the database command corresponding to each HTTP method is predetermined.

Furthermore, the conversion logic data L associates a processing type indicating whether a command for the table is performed by synchronous processing or asynchronous processing. For example, in the example shown in FIG. 4, the HTTP method “GET” corresponds to the SQL command “SELECT” and is a synchronization process. The HTTP method “POST” corresponds to the SQL command “INSERT” and is an asynchronous process.

The processing device 20 includes a table structure acquisition unit 21, a conversion logic generation unit 22, and a conversion logic provision unit 24.

When an instruction to register an API is input from the application development device 6, the table structure acquisition unit 21 acquires the table structure data 11 for each table in the database used in the API processing and stores it in the storage device 10. To do. For example, the application development apparatus 6 specifies the DBM IP address, port number, and the like, specifies the target database by the table structure acquisition unit 21, and sets the table structure data 11 for each table accommodated in the specified database. You may get

The conversion logic generation unit 22 generates conversion logic data L with reference to the table structure data 11 and the selection logic data 12. The conversion logic generation unit 22 performs (1) conversion of an HTTP method and a command for manipulating DBM data, (2) conversion of a URI and DBM table or view specified by HTTP, and (3) HTTP, as in the past. The parameter specified in (1) and the DBM attribute are converted. The conversion logic generation unit 22 according to the embodiment of the present invention further includes (4) a processing type determination unit 23 that sets a processing type to be performed by synchronous processing or asynchronous processing.

The process type determination unit 23 refers to the selection logic data 12 and identifies a database table and command that match the conditions of the selection logic data 12 and the process type. In the conversion logic data L, the processing type determination unit 23 associates the HTTP method corresponding to the specified command, the processing target of the HTTP method corresponding to the specified table, and the processing type of the specified command. When determining the processing type according to the table structure, the processing type determination unit 23 also considers the table structure data 11. The processing type determination unit 23 refers to the table structure data 11 or other necessary data in order to determine whether or not the command for the database table satisfies the condition defined by the selection logic data 12. You may do it.

For example, in the selection logic data 12, when an asynchronous process is associated as a process type with respect to a condition that requires time for execution on the table, the process type determination unit 23 identifies a command and a table that require time to execute To do. The processing type determination unit 23 updates the conversion logic data L by associating asynchronous processing as the processing type with the HTTP method corresponding to this command and the processing target for this table for the specified command and table.

Further, in the selection logic data 12, when an asynchronous process is associated as a process type with respect to the condition “with access to other tables in the database”, the process type determining unit 23 executes the command for the table. Identify commands and tables to access other tables. The processing type determination unit 23 updates the conversion logic data L by associating asynchronous processing as the processing type with the HTTP method corresponding to this command and the processing target for this table for the specified command and table.

Further, in the selection logic data 12, for each table managed by the database management device 3, when associating the command to the database with the processing type of this command for this table, the processing type determination unit 23 determines from the selection logic data 12, The processing type is specified from the command corresponding to the HTTP method received from the application execution apparatus 7 and the table corresponding to the processing target of the HTTP method. The process type determination unit 23 outputs conversion logic data L in which the specified HTTP method, the processing target of the specified HTTP method, and the process type of the specified command are associated with each other.

As described above, the process type determination unit 23 refers to the selection logic data 12 and associates the conversion logic data L with the HTTP method and the process target corresponding to the command and the table by associating the asynchronous process or the synchronous process as the process type. Update.

When a command that takes a long time to process, such as a change of a plurality of tables, is performed in the synchronous process, a response cannot be returned within a predetermined time after the application execution apparatus 7 transmits the API, It may become. Therefore, the process type determination unit 23 assigns a synchronous process in principle, and an asynchronous process is exceptionally assigned to a command that takes a long time to process. Thereby, even when the application developer does not have knowledge of DBM, the application execution device 7 can avoid a situation in which a timeout occurs in the application and appropriately acquire the result.

The conversion logic providing unit 24 transmits the conversion logic data L generated by the conversion logic generation unit 22 to the HTTP method execution device 2. The conversion logic providing unit 24 may transmit the conversion logic data L to the HTTP method execution device 2 when the conversion logic data L is generated, or transmit it to the HTTP method execution device 2 when there is a request from the HTTP method execution device 2. May be.

With reference to FIG. 6, the conversion logic generation process by the conversion logic generation unit 22 according to the embodiment of the present invention will be described.

First, in step S101, the conversion logic generation unit 22 associates an HTTP method to be converted with a DB command. In step S102, the conversion logic generation unit 22 associates the processing target transmitted from the application with the DB table and attribute. The processes in steps S101 and S102 are performed in the same manner as in the past using the table shown in FIG.

Next, in step S103, the conversion logic generation unit 22 determines whether each table and database command corresponding to the processing target specified by the API is performed in a synchronous process or an asynchronous process according to the selection logic data 12. Specify the processing type to be shown. Alternatively, the conversion logic generation unit 22 may specify a table and a command to be executed by asynchronous processing according to the selection logic data 12, and may specify each processing type when the other table and command are executed by asynchronous processing.

In step S104, the conversion logic generation unit 22 generates the conversion logic data L based on the processing results in steps S101 to S103. In the embodiment of the present invention, the conversion logic generation unit 22 sets the processing type when executing the command corresponding to the HTTP method for the table and the attribute corresponding to the processing target for the HTTP method and the processing target. The conversion logic data L is generated in association with the processing type specified in S103.

(HTTP method execution device)
With reference to FIG. 7, the HTTP method execution apparatus 2 which concerns on embodiment of this invention is demonstrated. The HTTP method execution device 2 is a general computer including a storage device 50, a processing device 60, and a communication control device 70. A general computer executes the HTTP method execution program to realize the functions shown in FIG.

The storage device 50 is a read only memory (ROM), a random access memory (RAM), a hard disk, and the like, and stores various data such as input data, output data, and intermediate data for the processing device 60 to execute processing. . The processing device 60 is a CPU (Central Processing Unit) and reads / writes data stored in the storage device 50 and inputs / outputs data to / from the communication control device 70 to perform processing in the HTTP method execution device 2. Execute. The communication control device 70 is an interface for allowing the HTTP method execution device 2 to connect to the conversion logic generation device 1 and the database management device 3 so that they can communicate with each other.

Storage device 50 stores conversion logic data L and processing result data 51.

The conversion logic data L is data generated by the conversion logic generation device 1 and described with reference to FIG.

The processing result data 51 holds the processing result when the asynchronous processing is performed on the database. As shown in FIG. 8, the processing result data 51 holds an inquiry URI assigned to the asynchronous processing performed on the database in association with the identifier (link) of the processing result of the asynchronous processing.

The processing device 60 includes a conversion logic acquisition unit 61, an application request processing unit 62, a conversion unit 63, and a database request processing unit 64.

The conversion logic acquisition unit 61 acquires the conversion logic data L from the conversion logic generation device 1 and stores it in the storage device 50. The conversion logic acquisition unit 61 may acquire the conversion logic data L when receiving a processing request from the application execution device 7 or may acquire the conversion logic data L in advance.

The application request processing unit 62 receives a request including an HTTP method and a processing target from the application execution device 7. The application request processing unit 62 further returns the processing request processing result to the application execution device 7.

The conversion unit 63 refers to the conversion logic data L, converts the processing request into a database request for the database, and determines the processing type of the command from the HTTP method included in the processing request and the processing target included in the processing request. To do. The conversion unit 63 converts the HTTP method specified in the processing request into a database command, and converts the processing target specified in the processing request into an attribute of a database table. Furthermore, the conversion unit 63 specifies a processing type indicating whether to perform synchronous processing or asynchronous processing on the HTTP method and processing target specified in the processing request.

The database request processing unit 64 processes the database request converted by the conversion unit 63 based on the processing type determined by the conversion unit 63. The database request processing unit 64 includes a synchronous processing unit 65 that accesses the database by synchronous processing, and an asynchronous processing unit 66 that accesses the database by asynchronous processing.

The synchronization processing unit 65 immediately processes the database request and returns it to the application execution device 7. Specifically, when the processing type determined by the conversion unit 63 is synchronous processing, the synchronization processing unit 65 transmits a database request to the database management device 3 and transmits a processing result received from the database management device to the application execution device 7. To do.

The asynchronous processing unit 66 creates an inquiry URI and returns it to the application execution device 7 without processing the database request immediately, and processes the database request. Specifically, when the processing type determined by the conversion unit 63 is asynchronous processing, the asynchronous processing unit 66 transmits a processing response including an inquiry URI that provides a processing result for the processing request to the application execution device 7. In addition, the synchronization processing unit 65 transmits a database request to the database management device 3 and stores the processing result received from the database management device 3 in the processing result data 51 in association with the inquiry URI.

When the asynchronous processing unit 66 receives an inquiry request including an inquiry URI from the application execution device 7 before holding the processing result received from the database management device 3 in the processing result data 51, the asynchronous processing unit 66 indicates that the processing is incomplete. Return to execution device 7. On the other hand, when the asynchronous processing unit 66 holds the processing result received from the database management device 3 in the processing result data 51 and then receives an inquiry request including the inquiry URI from the application execution device 7, the asynchronous processing unit 66 sends the processing result to the application execution device 7. return.

(Concrete example)
Referring to FIG. 9 to FIG. 12, taking the specific table managed by the database management device 3 as an example, the conversion logic generation device 1 asynchronously processes the command for the condition “with access to other tables in the database”. An example of determining that will be described.

FIG. 9 is an example of a customer table T1, a product table T2, and an order list table T3 managed by the database management apparatus 3. The “customer address” in the order list table T3 has a relationship with the “customer ID” in the customer table T1, and the “product name” in the order list table T3 has a relationship with the “product ID” in the product table T2. .

The table structure data of the customer table T1 is shown in FIG. 10 (a), and the correspondence between the notation in the table structure data and the notation in FIG. 9 is shown in FIG. 10 (b). Similarly, in the product table T2 and the order list table T3, the table structure data is shown in FIG. 11A and FIG. 12A, and the correspondence between the notation in the table structure data and the notation in FIG. It is shown in b) and FIG.

Here, the table structure data of the order name list table T3 shown in FIG. 12A indicates that “customer address (customer_address)” and “product name (product_name)” are “FOREIGN KEY”. Each item indicates that “customer_id” and “product_id” in another table are referred to.

Here, it is assumed that, in the selection logic data 12 of the conversion logic generation device 1, it is set that asynchronous processing is performed for the condition “with access to other tables in the database”. In the structure data of the order name list table shown in FIG. 12, there is a foreign key “FOREIGN KEY”, that is, a relation. INSERT and UPDATE commands with additions or changes to the order list table T3 involve access to other tables. Accordingly, the process type determination unit 23 determines that the HTTP method POST and PUT corresponding to INSERT and UPDATE are to be performed asynchronously for the order name list table T3 shown in FIG. The processing type determination unit 23 determines that the HTTP method GET and DELETE corresponding to the commands other than INSERT and UPDATE are to be performed in a synchronous process with respect to the order name list table T3 shown in FIG.

Note that the selection logic data 12 described here is an example, and the present invention is not limited to this. For example, in the selection logic data 12, it may be set that asynchronous processing is performed for the condition “with access to two or more other tables in the database”. Further, the condition of “command for a table having a predetermined number of records or more” may be set to be asynchronous processing. In addition, it is possible to set asynchronous processing for conditions that are empirically determined that processing takes time and combinations of tables and commands that are empirically determined to require processing. Further, in actual operation, a combination of a table and a command determined to take a long time for processing may be set to be asynchronous processing.

The conversion logic generation device 1 according to the embodiment of the present invention corresponds to the selection logic data 12 in advance with a table and a processing type indicating whether a command for the table is an asynchronous process or a synchronous process. Put it on. Since the conversion logic generation device 1 outputs the conversion logic data L in which the processing type is associated with the HTTP method and the processing target based on the selection logic data 12, the HTTP method execution device 2 receives the API from the HTTP method. When creating, synchronous processing or asynchronous processing can be optimally selected. As a result, the developer of the application that transmits the API does not need to set the processing type of the synchronous process or the asynchronous process for the API command, and therefore specifies the processing type of the API command even if the database mechanism is not well known. be able to. In addition, since the processing type can be set appropriately, the application execution device 7 can acquire the result without causing a shortage such as a timeout occurring in the application.

(Other embodiments)
As described above, the embodiments of the present invention have been described. However, it should not be understood that the descriptions and drawings constituting a part of this disclosure limit the present invention. From this disclosure, various alternative embodiments, examples, and operational techniques will be apparent to those skilled in the art.

For example, the conversion logic generation device described in the embodiment of the present invention may be configured on one piece of hardware as shown in FIG. 3, or on a plurality of pieces of hardware according to the functions and the number of processes. It may be configured. Moreover, you may implement | achieve on the existing information processing system.

Of course, the present invention includes various embodiments not described herein. Therefore, the technical scope of the present invention is defined only by the invention specifying matters according to the scope of claims reasonable from the above description.

DESCRIPTION OF SYMBOLS 1 Conversion logic production | generation apparatus 2 HTTP method execution apparatus 3 Database management apparatus 4, 8 Communication network 5 HTTP method execution system 6 Application development apparatus 7 Application execution apparatus 9

Information processing system

10, 50

Storage apparatus

30, 70 Communication control apparatus 11 Table structure Data 12

Selection logic data

20, 60 Processing device 21 Table structure acquisition unit 22 Conversion logic generation unit 23 Processing type determination unit 24 Conversion logic provision unit 51 Processing result data 61 Conversion logic acquisition unit 62 Application request processing unit 63 Conversion unit 64 Database request Processing unit 65 Synchronization processing unit L Conversion logic data

Claims

A conversion logic generation device that generates conversion logic data for converting an HTTP method received from an application execution device into a database command,
A storage device that stores selection logic data that associates a process type indicating whether the command for the table of the database is performed in a synchronous process or an asynchronous process, and a condition for applying the process type;
With reference to the selection logic data, the table and the command that match the condition and the processing type are specified, the HTTP method corresponding to the specified command, and the processing target of the HTTP method corresponding to the specified table And a conversion logic generation unit that outputs conversion logic data in which the specified processing type of the command is associated.
The selection logic data is
The conversion logic generation device according to claim 1, wherein an asynchronous process is associated as the process type with a condition that requires time to execute the table.
The selection logic data is
The conversion logic generation device according to claim 1, wherein an asynchronous process is associated as the process type with a condition involving access to another table of the database.
A conversion logic generation device that generates conversion logic data for converting an HTTP method received from the application execution device into a database command, and an HTTP that converts the HTTP method into a database command based on the conversion logic data and executes the conversion method An HTTP method execution system comprising a method execution device and a database management device for managing the database,
The conversion logic generation device includes:
A storage device that stores selection logic data that associates a process type indicating whether the command for the table of the database is performed in a synchronous process or an asynchronous process, and a condition for applying the process type;
With reference to the selection logic data, the table and the command that match the condition and the processing type are specified, the HTTP method corresponding to the specified command, and the processing target of the HTTP method corresponding to the specified table And a conversion logic generation unit that outputs conversion logic data in which the specified processing type of the command is associated,
The HTTP method execution device is:
An application request processing unit that receives a processing request including the HTTP method and a processing target from the application execution device;
With reference to the conversion logic data, the processing request is converted into a database request for the database, and the processing type of the command is determined from the HTTP method included in the processing request and the processing target included in the processing request. A conversion unit to determine;
An HTTP method execution system comprising: a database request processing unit that processes the database request based on a processing type determined by the conversion unit.
The database request processing unit
When the processing type determined by the conversion unit is synchronous processing,
A synchronization processing unit for transmitting the database request to the database management device and transmitting a processing result received from the database management device to the application execution device;
When the processing type determined by the conversion unit is asynchronous processing,
A processing response including a query URI that provides a processing result for the processing request is transmitted to the application execution device, the database request is transmitted to the database management device, and the processing result received from the database management device is represented by the query URI. The HTTP method execution system according to claim 5, further comprising: an asynchronous processing unit that stores the data in association with each other.
A conversion logic generation device that generates conversion logic data for converting an HTTP method received from the application execution device into a database command, and an HTTP that converts the HTTP method into a database command based on the conversion logic data and executes the conversion method An HTTP method execution method used in an HTTP method execution system comprising a method execution device and a database management device for managing the database,
A step of storing selection logic data in which the conversion logic generation device associates a processing type indicating whether the command for the table of the database is executed in a synchronous process or an asynchronous process with a condition for applying the processing type; When,
The conversion logic generation device refers to the selection logic data, identifies the table and command that match the condition, and the processing type, and corresponds to the HTTP method corresponding to the identified command and the identified table. Outputting conversion logic data associating the processing target of the HTTP method with the processing type of the specified command;
The HTTP method execution device receiving a processing request including the HTTP method and a processing target from the application execution device;
The HTTP method execution device refers to the conversion logic data, converts the processing request into a database request for the database, and also includes the HTTP method included in the processing request and the processing target included in the processing request. Determining the processing type of the command;
The HTTP method execution device comprises the step of processing the database request based on the determined processing type.
A conversion logic generation program for causing a computer to function as the conversion logic generation device according to any one of claims 1 to 3.