KR102262093B1 - Gateway apparatus, and control method thereof - Google Patents

Abstract

The present invention relates to a gateway device capable of providing micro-services to clients in an integrated environment in which scientific and technological knowledge infrastructures of individual fields are linked with each other and an operating method thereof.

Description

Gateway device and its operation method {GATEWAY APPARATUS, AND CONTROL METHOD THEREOF}

The present invention relates to a method for providing microservices to clients in an integrated environment in which scientific and technological knowledge infrastructures of individual fields are linked with each other.

Thanks to the development of scientific and technological knowledge infrastructure and related technologies in various fields, API services that provide responses to various queries requested by clients in the form of API (Application Programming Interface) are becoming common.

However, recently, there is an increasing demand for microservices that can be changed and combined by dividing one API service provided by the science and technology knowledge infrastructure in each field into small units.

Moreover, in order to meet the ever-evolving needs of clients, it is necessary to build an integrated science and technology knowledge infrastructure that links the science and technology knowledge infrastructures of individual fields with each other.

Accordingly, in the present invention, it is intended to propose a new method for providing microservices in an integrated environment in which scientific and technological knowledge infrastructures of individual fields are linked with each other.

The present invention was created in view of the above circumstances, and an object of the present invention is to provide microservices to clients in an integrated environment in which scientific and technological knowledge infrastructures of individual fields are linked with each other.

In a gateway device according to an embodiment of the present invention for achieving the above object, when a query is received from a client, the received query is a package query that requires calls of two or more API servers providing respective microservices. Confirmation unit to check whether it is recognized; a determination unit that determines whether there is a sequence attribute that the package query may have; and a routing unit that calls the two or more API servers according to a calling method based on the determination result, and transmits a response to the query received from the client when a response to the call is confirmed from the two or more API servers characterized in that

Specifically, when it is requested that the result of the call to a specific API server among the two or more API servers from the package query be an input value of any one API server other than the specific API server, the package query It can be determined that the order attribute exists in .

Specifically, when a response to a call is not received from a specific API server among the two or more API servers, the routing unit makes a call to the specific API server according to a call method according to the order attribute present in the package query. Can be repeated.

Specifically, when calls to each of the two or more API servers are collectively requested from the package query, the determination unit may determine that the order attribute does not exist in the package query.

Specifically, the gateway device, when it is determined that the order attribute does not exist in the package query, further includes a message conversion unit for converting a synchronous (Sync) type query received from the client into an asynchronous (Async) method can do.

Specifically, the routing unit may collectively call the two or more API servers according to the asynchronous method so that responses from each API server are received according to a response speed supported by the two or more API servers.

Specifically, in the gateway device, when a REST (Representational State Transfer) message is used between the client and the gateway device, and a binary message is used between the gateway device and the API server, the protocol between the REST message and the binary message is It may further include a message protocol conversion unit for converting.

Specifically, the gateway device, when it is possible to call two or more API servers providing the same microservice according to a query received from the client, based on at least one of performance and failure occurrence of each of the two or more API servers It may further include a load balancing unit that sets a weight for each of the two or more API servers, so that the two or more API servers are called according to the set weight.

Specifically, the gateway device issues a token to the client by performing authentication based on authentication information received from the client, and only when the token issued from the client transmitting the query is confirmed It may further include a security processing unit for authorizing the call of the API server for the query from the client.

In a method of operating a gateway device according to an embodiment of the present invention for achieving the above object, when a query is received from a client, the received query requires calls of two or more API servers providing respective microservices. A confirmation step of checking whether it is a package query; a determining step of determining whether there is a sequence attribute that the package query can have; and a routing step of calling the two or more API servers according to a calling method based on the determination result, and transmitting a response to the query received from the client when a response to the call is confirmed from the two or more API servers characterized in that

Specifically, in the determining step, when it is requested that the result of a call to a specific API server among the two or more API servers from the package query be an input value of any one API server other than the specific API server, the package It may be determined that the order attribute exists in the query.

Specifically, in the routing step, when a response to a call is not received from a specific API server among the two or more API servers, a call is made to the specific API server according to a calling method according to the order attribute present in the package query. can be repeated.

Specifically, in the determining step, when calls to each of the two or more API servers are collectively requested from the package query, it may be determined that the order attribute does not exist in the package query.

Specifically, when it is determined that the order attribute does not exist in the package query, the method further includes a message conversion step of converting a synchronous type query received from the client to an asynchronous (Async) method can do.

Specifically, in the routing step, the two or more API servers are collectively called according to the asynchronous method, so that responses from each API server are received according to a response speed supported by the two or more API servers.

Specifically, in the method, when a REST (Representational State Transfer) message is used between the client and the gateway device, and a binary message is used between the gateway device and the API server, a protocol between the REST message and the binary message is converted It may further include a message protocol conversion step.

Specifically, in the method, when two or more API servers providing the same microservice can be called according to a query received from the client, based on at least one of the performance and failure of each of the two or more API servers, the By setting weights for each of the two or more API servers, the two or more API servers may be called according to the set weights.

Specifically, the method issues a token to the client by performing authentication based on authentication information received from the client, and only when the token issued from the client transmitting the query is confirmed It may further include a security processing step of authorizing the call of the API server for the query from the client (Authorization).

Accordingly, in the gateway device and its operating method of the present invention, an environment is provided that can provide microservices to the client 100 in an integrated environment in which scientific and technological knowledge infrastructures of individual fields are linked with each other, thereby greatly increasing user satisfaction. enhancement effect can be achieved.

1 is an exemplary diagram for explaining an integrated science and technology knowledge infrastructure environment according to an embodiment of the present invention.
2 is a schematic configuration diagram of a gateway device according to an embodiment of the present invention;
3 is an exemplary diagram for explaining a security processing method according to an embodiment of the present invention.
4 is an exemplary diagram for explaining a message conversion method according to an embodiment of the present invention.
5 is a flowchart illustrating a method of operating a gateway device according to an embodiment of the present invention.

Hereinafter, preferred embodiments of the present invention will be described with reference to the accompanying drawings.

In one embodiment of the present invention, a technology for providing microservices to clients in an integrated environment in which scientific and technological knowledge infrastructures of individual fields are interconnected is dealt with.

In this regard, thanks to the construction of scientific and technological knowledge infrastructure in various fields and the development of related technologies, in the scientific and technological knowledge infrastructure of each individual field, responses to various queries requested from clients are provided by API (Application Programming Interface). ) in the form of API services.

Recently, according to the needs of clients, there is an increasing demand for providing a microservice in a form that can be changed and combined by dividing one API service provided by the science and technology knowledge infrastructure in each field into small units. to be.

Moreover, in order to meet the evolving needs of clients, it is not limited to providing microservices in units of science and technology knowledge infrastructure in each field, but in an integrated science and technology knowledge infrastructure environment that connects each individual science and technology knowledge infrastructure with each other. We need to provide microservices.

Accordingly, the present invention intends to propose a new method for providing microservices to clients in an integrated environment in which scientific and technological knowledge infrastructures of individual fields are linked with each other.

In this regard, FIG. 1 exemplarily shows an integrated science and technology knowledge infrastructure environment according to an embodiment of the present invention.

As shown in FIG. 1 , in the integrated science and technology knowledge infrastructure environment according to an embodiment of the present invention, each microservice is provided in the integrated service infrastructure 300 for a query requested from the client 100 . A configuration of the gateway device 200 that calls the provided API server and transmits a corresponding response to the client 100 is proposed.

Here, the client 100 refers to a device that transmits an HTTP-based query to the gateway device 200 and receives a corresponding response from the gateway device 200 , for example, installed on a desktop or mobile computing device. It may be implemented in the form of an application (Application).

The gateway device 200 refers to a device capable of standardizing the end-point of all API servers in the integrated service infrastructure 300 at the front end of the integrated service infrastructure 300, for example, authentication/authorization for API or client ( 100) is responsible for various functions, including the ability to route messages to each microservice (API server).

For reference, the gateway device 200 may be implemented in the form of a proxy server, etc., and one or more of a variety of software that allows a network load balancing mechanism, or a service device to operate on the Internet or other networks may be installed. , through which it can also be implemented as a computerized system.

As described above, in the integrated science and technology knowledge infrastructure environment according to an embodiment of the present invention, microservices can be provided to the client 100 in the integrated environment in which the science and technology knowledge infrastructures of individual fields are linked with each other through the above configuration. The configuration of the gateway device 200 for realizing this will be described in more detail.

2 shows a schematic configuration of a gateway device 200 according to an embodiment of the present invention.

As shown in FIG. 2 , the gateway device 200 according to an embodiment of the present invention checks the checking unit 210 for checking the properties of the query received from the client 100 and the sequence property. The determination unit 220 for determining, the message conversion unit 230 for performing message conversion between the synchronous (Sync) method and the asynchronous (Async) method, the routing unit 240 for routing the query, and the client 100 It may have a configuration including a response unit 250 that delivers a response to a query.

This, the combination of the above configuration including the confirmation unit 210, the determination unit 220, the message conversion unit 230, the routing unit 240, and the response unit 250, orchestration in an embodiment of the present invention (Ochestration), which can be understood as a concept of providing a new service by tying several APIs into one API.

In addition, the gateway device 200 according to an embodiment of the present invention may further include a message protocol conversion unit 260 for converting a message protocol in addition to the above-described configuration.

Here, the combination of the above-described configuration corresponding to the orchestration and the configuration including the message protocol conversion unit 260 may be collectively referred to as routing filters in an embodiment of the present invention.

In addition, the gateway device 200 according to an embodiment of the present invention includes, in addition to the above-described configuration, the load ban lancing unit 270 for processing load distribution between API servers, and authentication and authorization for the client 100 . ) may further include a security processing unit 280 for processing, and a logging unit 290 for managing API call logs.

Here, the configuration combination including the load ban lancing unit 270 , the security processing unit 280 , and the logging unit 290 may be collectively referred to as pre-routing filters in an embodiment of the present invention.

The entire configuration or at least a part of the above-mentioned gateway device 200 may be implemented in the form of a software module or a hardware module, or may be implemented in a form in which a software module and a hardware module are combined.

Here, the software module may, for example, be implemented in the form of a filter, which is a function executed by a processor that performs an operation within the gateway device 200, and these filters are inquired through a separate manager. , input, modification, and deletion are possible.

As described above, the gateway device 200 according to an embodiment of the present invention can provide microservices to the client 100 in an integrated environment in which scientific and technological knowledge infrastructures of individual fields are linked with each other through the above-described configuration. A more detailed description of each configuration in the gateway device 200 for realizing this will be continued.

In particular, in the following description, the description will be continued focusing on the configuration of the orchestration corresponding to the core configuration of the gateway device 200 .

The check unit 210 performs a function of checking a query from the client 100 .

More specifically, when a query (Query) is received from the client 100, the check unit 210 checks whether the received query is a package query that requires calls of two or more API servers providing each microservice. do.

Meanwhile, in relation to the performance of the function of the verification unit 210 , the security processing unit 280 processes authentication and authorization for the client 100 .

That is, as shown in FIG. 3 (a), the security processing unit 280 issues a token to the client 100 by performing authentication based on the authentication information received from the client 100, and then , as shown in Fig. 3(b), only when the token issued from the client that transmits the query (API call) is confirmed, the call of the API server is authorized for the query of the client 100 (Authorization).

In other words, the client 100 does not receive a user ID and password every time, but is issued a separate token that can call the API, and through this, the token and token storage that are checked from the client 100 every time a query (API call) is made. Whether or not an API call to the client 100 is possible may be determined according to a result of comparing the data previously stored in the .

For reference, Authorization in an embodiment of the present invention is a procedure to check whether or not there is an authority to call an API. For example, assuming that there are general users and administrators, by issuing tokens for each role, Depending on the role identified from the token, the corresponding API call permission can be granted.

The determination unit 220 performs a function of determining whether a sequence attribute exists.

More specifically, when it is confirmed from the client that the query is a package query, the determination unit 220 determines whether there is a sequence attribute that the package query can have.

At this time, when it is requested that the result of a call to a specific API server among two or more API servers from the package query be the input value of any one API server except for the specific API server, the determination unit 220 may send the order attribute to the package query. can be judged to exist.

On the other hand, when calls to each of two or more API servers are collectively requested from the package query, the determination unit 22 determines that the order attribute does not exist in the package query.

The message conversion unit 230 performs a function of converting a message.

More specifically, the message conversion unit 230 converts a synchronous (Sync) type query received from the client 100 into an asynchronous (Async) method when it is determined that the order attribute does not exist in the package query. Message conversion is performed.

In relation to this, in the message call pattern in an embodiment of the present invention, there may be a synchronous (Sync) call and an asynchronous (Async) call, and for this, an asynchronous API call is converted into a synchronous call, or one API call is converted into several microcontrollers. It is possible to change the message pattern in the form of replication to the service database.

In particular, when the API server cannot process large-capacity traffic, for example, as shown in FIG. 4 , a response (ACK) is immediately transmitted when a query is received from a client, and then a message queue is used to Depending on the performance of the API server, it is possible to store the corresponding message.

Accordingly, it is a synchronous call from the client's point of view, but the actual message flow can be changed to an asynchronous structure using a queue.

The routing unit 240 performs a function of processing a call to the API server.

More specifically, the routing unit 240 calls two or more API servers according to a calling method according to the presence or absence of an order attribute that may have a package query, and when a response to the call is confirmed from two or more API servers, a response Allows unit 250 to forward a response to a query received from client 100 .

In this case, the routing unit 240 requires that the result of a call to a specific API server among two or more API servers be the input value of any one API server other than the specific API server according to the order attribute of the package query. , after waiting for the result of a call to a specific API server, the call result received from the specific API server is delivered as an input value of any one of the other API servers.

On the other hand, when a response to the call is not received from the specific API server in this process, the routing unit 240 repeats the call to the specific API server according to the calling method according to the order attribute present in the package query.

On the other hand, the routing unit 240 determines that the order attribute does not exist in the package query and when the synchronous query received from the client 100 is switched to the asynchronous method, 2 according to the asynchronous method The above API servers are collectively called, so that responses from each API server are received according to the response speed supported by two or more API servers, and when a response from the last API server is received, the response unit 250 causes the client ( 100) to deliver a response to a query received from

On the other hand, in relation to the performance of the function of the routing unit 240, the message protocol conversion unit 260 may perform a function of converting the message protocol.

That is, the message protocol conversion unit 260 uses a REST (Representational State Transfer) message between the client 100 and the gateway device 200, and when a binary message is used between the gateway device 200 and the API server, REST message and the protocol conversion between binary messages.

In other words, when the gateway device 200 supports various microservices or clients, there may be a case in which a different communication protocol must be used for each client 100 or microservice.

In this regard, in an embodiment of the present invention, a JSON-based REST message is used between the client 100 and the gateway device 200, but a binary message for improving the transmission speed between the gateway device 200 and the API server is used. In this regard, by converting the protocol between REST message and binary message, internal API performance can be increased through binary message, and versatility can be secured by using REST message externally.

Also, the load balancing unit 270 may handle load balancing between API servers.

That is, when two or more API servers that provide the same microservice can be called according to a query received from the client 100, the load balancing unit 270 determines at least one of the performance and failure of each of the two or more API servers. By setting a weight for each of the two or more API servers based on it, two or more API servers may be called according to the set weight.

In other words, the load balancing unit 270 can distribute the load based on the performance according to the hardware specifications of each API server for a general call, and when an API server failure occurs, the load balancing list of the failed API server It can be implemented so that it cannot participate in load balancing by deleting it from , and can participate in load balancing by adding it to the load balancing list when recovering from a subsequent failure.

Also, the logging unit 290 may manage an API call log according to a query received from the client 100 .

That is, in an embodiment of the present invention, the gateway device 200 is located in front of the integrated service infrastructure 300 where all API servers are located, so by managing the API call log corresponding to the query received from the client 100 , , through this, it is possible to derive each user's usage pattern based on API call pattern analysis, or to use it as audit data for problem tracking.

As described above, according to the configuration of the gateway device 200 according to an embodiment of the present invention, it is possible to provide microservices to the client 100 in an integrated environment in which scientific and technological knowledge infrastructures of individual fields are linked with each other. As an environment is provided, user satisfaction can be greatly improved. In addition, as the message protocol conversion function is supported, it becomes easy to integrate new microservices into the existing infrastructure, thereby enabling change and expansion of the service area. In addition, as the API call log is managed, it is possible to derive each user's usage pattern and facilitate recognition and recovery in case of a failure.

After the description of the configuration of the gateway device 200 according to an embodiment of the present invention has been completed, the description of the operation method of the gateway device 200 will be continued with reference to FIG. 5 .

In particular, in the following description, the description will be continued focusing on the operation method of the orchestration corresponding to the core configuration of the gateway device 200 .

First, when a query is received from the client 100 , the check unit 210 checks whether the received query is a package query that requires calls of two or more API servers providing respective microservices (S10). ).

Meanwhile, in relation to the performance of the function of the verification unit 210 , the security processing unit 280 processes authentication and authorization for the client 100 .

That is, the security processing unit 280 issues a token to the client 100 by performing authentication based on the authentication information received from the client 100 , and thereafter, from the client that transmits the query (API call) Only when the issued token is confirmed, the call of the API server is authorized for the query of the client 100 (Authorization).

In other words, the client 100 does not receive a user ID and password every time, but is issued a separate token that can call the API, and through this, the token and token storage that are checked from the client 100 every time a query (API call) is made. Whether or not an API call to the client 100 is possible may be determined according to a result of comparing the data previously stored in the .

For reference, Authorization in an embodiment of the present invention is a procedure to check whether or not there is an authority to call an API. For example, assuming that there are general users and administrators, by issuing tokens for each role, Depending on the role identified from the token, the corresponding API call permission can be granted.

Then, when it is confirmed from the client that the query is a package query, the determination unit 220 determines whether there is a sequence attribute that the package query can have ( S20 ).

At this time, when it is requested that the result of a call to a specific API server among two or more API servers from the package query be the input value of any one API server except for the specific API server, the determination unit 220 may send the order attribute to the package query. can be judged to exist.

On the other hand, when calls to each of two or more API servers are collectively requested from the package query, the determination unit 22 determines that the order attribute does not exist in the package query.

On the other hand, the message conversion unit 230 asynchronously (Async) the query received from the client 100 in the case where it is determined that the order attribute does not exist in the package query in the previous step 'S30'. A message conversion is performed to switch the method (S30-S40).

In relation to this, in the message call pattern in an embodiment of the present invention, there may be a synchronous (Sync) call and an asynchronous (Async) call, and for this, an asynchronous API call is converted into a synchronous call, or one API call is converted into several micro It is possible to change the message pattern in the form of replication to the service database.

In particular, when the API server cannot handle large-capacity traffic, the response (ACK) is immediately delivered when a query is made from the client, and then the corresponding message is sent according to the API server's performance using a message queue. It is possible to save

Accordingly, it is a synchronous call from the client's point of view, but the actual message flow can be changed to an asynchronous structure using a queue.

Thereafter, the routing unit 240 calls two or more API servers according to a call method according to the presence or absence of an order attribute that may have a package query, and when a response to the call is confirmed from two or more API servers, the response unit ( 250) to deliver a response to the query received from the client 100 (S50-S60).

In this case, the routing unit 240 requires that the result of a call to a specific API server among two or more API servers be the input value of any one API server other than the specific API server according to the order attribute of the package query. , after waiting for the result of a call to a specific API server, the call result received from the specific API server is delivered as an input value of any one of the other API servers.

On the other hand, if a response to the call is not received from the specific API server in this process, the routing unit 240 repeats the call to the specific API server according to a call method according to the order attribute present in the package query.

On the other hand, the routing unit 240 determines that the order attribute does not exist in the package query and when the synchronous query received from the client 100 is switched to the asynchronous method, 2 according to the asynchronous method The above API servers are collectively called, so that responses from each API server are received according to the response speed supported by two or more API servers, and when a response from the last API server is received, the response unit 250 causes the client ( 100) to deliver a response to a query received from

On the other hand, in relation to the performance of the function of the routing unit 240, the message protocol conversion unit 260 may perform a function of converting the message protocol.

That is, the message protocol conversion unit 260 uses a REST (Representational State Transfer) message between the client 100 and the gateway device 200, and when a binary message is used between the gateway device 200 and the API server, REST message and the protocol conversion between binary messages.

In other words, if the gateway device 200 supports various microservices or clients, there may be cases in which a different communication protocol must be used for each client 100 or microservice.

In this regard, in an embodiment of the present invention, a JSON-based REST message is used between the client 100 and the gateway device 200, but a binary message for improving the transmission speed between the gateway device 200 and the API server is used. In this regard, by converting the protocol between REST message and binary message, internal API performance can be increased through binary message, and versatility can be secured by using REST message externally.

Also, the load balancing unit 270 may handle load balancing between API servers.

That is, when two or more API servers that provide the same microservice can be called according to a query received from the client 100 , the load balancing unit 270 determines at least one of the performance and failure of each of the two or more API servers. By setting a weight for each of the two or more API servers based on it, two or more API servers may be called according to the set weight.

In other words, the load balancing unit 270 can distribute the load based on the performance according to the hardware specifications of each API server for a general call, and when an API server failure occurs, the load balancing list of the failed API server It can be implemented so that it cannot participate in load balancing by deleting it from , and can participate in load balancing by adding it to the load balancing list when recovering from a subsequent failure.

Also, the logging unit 290 may manage an API call log according to a query received from the client 100 .

That is, in an embodiment of the present invention, the gateway device 200 is located in front of the integrated service infrastructure 300 where all API servers are located, so by managing the API call log corresponding to the query received from the client 100 , , through this, it is possible to derive each user's usage pattern based on API call pattern analysis, or to use it as audit data for problem tracking.

As described above, according to the operation method of the gateway device 200 according to an embodiment of the present invention, it is possible to provide microservices to the client 100 in an integrated environment in which scientific and technological knowledge infrastructures of individual fields are linked with each other. As an environment is provided, the user's satisfaction can be greatly improved. In addition, as the message protocol conversion function is supported, it becomes easy to integrate new microservices into the existing infrastructure, thereby enabling change and expansion of the service area. In addition, as the API call log is managed, it is possible to derive each user's usage pattern and facilitate recognition and recovery in case of a failure.

On the other hand, the functional operations and implementations of the subject matter described in this specification are implemented as digital electronic circuits, computer software, firmware or hardware including the structures disclosed in this specification and structural equivalents thereof, or at least one of these It can be implemented by combining. Implementations of the subject matter described herein are one or more computer program products, ie, one or more modules of computer program instructions encoded on a tangible program storage medium for processing or execution by a processing system. can be implemented.

The computer-readable medium may be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter that affects a machine-readable radio wave signal, or a combination of one or more thereof.

As used herein, the term “system” or “device” encompasses all devices, devices and machines for processing data, including, for example, programmable processors, computers, or multiple processors or computers. The processing system may include, in addition to hardware, code that, upon request, forms an execution environment for a computer program, such as code constituting processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more thereof. .

A computer program (also known as a program, software, software application, script or code) may be written in any form of programming language, including compiled or interpreted language or declarative or procedural language, as a stand-alone program or module; It can be deployed in any form, including components, subroutines, or other units suitable for use in a computer environment. A computer program does not necessarily correspond to a file in a file system. A program may be in a single file provided to the requested program, or in multiple interacting files (eg, files that store one or more modules, subprograms, or portions of code), or portions of files that hold other programs or data. (eg, one or more scripts stored within a markup language document). The computer program may be deployed to be executed on a single computer or multiple computers located at one site or distributed over a plurality of sites and interconnected by a communication network.

On the other hand, computer-readable media suitable for storing computer program instructions and data include, for example, semiconductor memory devices such as EPROMs, EEPROMs and flash memory devices, such as magnetic disks such as internal hard disks or external disks, magneto-optical disks and CDs. -Can include all types of non-volatile memory, media and memory devices, including ROM and DVD-ROM disks. The processor and memory may be supplemented by, or incorporated into, special purpose logic circuitry.

An implementation of the subject matter described herein may include a backend component, such as a data server, or a middleware component, such as an application server, or a web browser or graphical user, such as a user capable of interacting with an implementation of the subject matter described herein. It may be implemented in a front-end component, such as a client computer having an interface, or in a computing system including any combination of one or more of such back-end, middleware, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication, such as, for example, a communication network.

While this specification contains numerous specific implementation details, they should not be construed as limitations on the scope of any invention or claim, but rather as descriptions of features that may be specific to particular embodiments of particular inventions. should be understood Likewise, certain features that are described herein in the context of separate embodiments may be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments, either individually or in any suitable subcombination. Furthermore, although features operate in a particular combination and may be initially depicted as claimed as such, one or more features from a claimed combination may in some cases be excluded from the combination, the claimed combination being a sub-combination. or a variant of a sub-combination.

Also, although operations are depicted in the drawings in a specific order herein, it is not to be understood that such operations must be performed in the specific order or sequential order shown or that all illustrated operations must be performed in order to achieve desirable results. Can not be done. In certain cases, multitasking and parallel processing may be advantageous. Further, the separation of the various system components of the above-described embodiments should not be construed as requiring such separation in all embodiments, and the program components and systems described may generally be integrated together into a single software product or packaged into multiple software products. It should be understood that

As such, this specification is not intended to limit the invention to the specific terminology presented. Accordingly, although the present invention has been described in detail with reference to the above-described examples, those skilled in the art can make modifications, changes, and modifications to the examples without departing from the scope of the present invention. The scope of the present invention is indicated by the following claims rather than the above detailed description, and all changes or modifications derived from the meaning and scope of the claims and their equivalent concepts should be interpreted as being included in the scope of the present invention. do.

According to the gateway device and the method of operation thereof according to the present invention, it is possible to provide microservices to clients in an integrated environment in which scientific and technological knowledge infrastructures of individual fields are linked with each other. It is an invention with industrial applicability because the possibility of marketing or business of the applied device, not just the use of it, is sufficient and it can be clearly implemented in reality.

100: client
200: gateway device
210: confirmation unit 220: determination unit
230: message conversion unit 240: routing unit
250: response unit 260: message protocol conversion unit
270: load balancing unit 280: security processing unit
290: logging unit
300: integrated service infrastructure

Claims (18)

When a query (Query) is received from the client, a check unit that checks whether the received query is a package query that requires calls of two or more API servers providing each microservice;
a determination unit that determines whether there is a sequence attribute that the package query may have; and
A routing unit that calls the two or more API servers according to a calling method based on the determination result, and transmits a response to a query received from the client when a response to the call is confirmed from the two or more API servers,
The judging unit,
When the call result for a specific API server among the two or more API servers from the package query is required to be an input value of any one API server except for the specific API server, the order attribute is present in the package query Gateway device, characterized in that it is determined. delete The method of claim 1,
The routing unit,
Gateway, characterized in that when a response to a call is not received from a specific API server among the two or more API servers, the call to the specific API server is repeated according to a call method according to the order attribute present in the package query Device. The method of claim 1,
The judging unit,
When the call to each of the two or more API servers is collectively requested from the package query, it is determined that the order attribute does not exist in the package query. The method of claim 1,
The gateway device,
When it is determined that the order attribute does not exist in the package query, the gateway device further comprising a message conversion unit for converting a synchronous (Sync) type query received from the client into an asynchronous (Async) method. 6. The method of claim 5,
The routing unit,
The gateway device, characterized in that by collectively calling the two or more API servers according to the asynchronous method, and receiving a response from each API server according to a response speed supported by the two or more API servers. The method of claim 1,
The gateway device,
When a REST (Representational State Transfer) message is used between the client and the gateway device, and a binary message is used between the gateway device and the API server, a message protocol conversion unit for converting a protocol between the REST message and the binary message is further included. Gateway device, characterized in that. The method of claim 1,
The gateway device,
When it is possible to call two or more API servers that provide the same microservice according to a query received from the client, based on at least one of the performance and failure of each of the two or more API servers, The gateway device according to claim 1, further comprising a load balancing unit that sets a weight so that the two or more API servers are called according to the set weight. The method of claim 1,
The gateway device,
A token is issued to the client by performing authentication based on the authentication information received from the client, and API for a query from the client only when the token issued from the client transmitting the query is confirmed Gateway device, characterized in that it further comprises a security processing unit for authorizing the call of the server (Authorization). When a query (Query) is received from the client, a checking step of confirming whether the received query is a package query that requires calls of two or more API servers providing each microservice;
a determination step of determining whether there is a sequence attribute that the package query can have; and
Including a routing step of calling the two or more API servers according to a calling method based on the determination result, and transmitting a response to the query received from the client when a response to the call is confirmed from the two or more API servers, ,
The judging step is
When the call result for a specific API server among the two or more API servers from the package query is required to be an input value of any one API server except for the specific API server, the order attribute is present in the package query Method of operation of a gateway device, characterized in that it is determined that it is. delete 11. The method of claim 10,
The routing step is
Gateway, characterized in that when a response to a call is not received from a specific API server among the two or more API servers, the call to the specific API server is repeated according to a call method according to the order attribute present in the package query How the device works. 11. The method of claim 10,
The judging step is
When the call to each of the two or more API servers is collectively requested from the package query, it is determined that the order attribute does not exist in the package query. 11. The method of claim 10,
The method is
When it is determined that the order attribute does not exist in the package query, the method further comprising a message conversion step of converting a Sync type query received from the client into an Async method. how it works. 15. The method of claim 14,
The routing step is
The method of operating a gateway device, characterized in that by collectively calling the two or more API servers according to the asynchronous method, a response from each API server is received according to a response speed supported by the two or more API servers. 11. The method of claim 10,
The method is
When a REST (Representational State Transfer) message is used between the client and the gateway device, and a binary message is used between the gateway device and the API server, a message protocol conversion step of converting a protocol between the REST message and the binary message is further performed. A method of operating a gateway device, comprising: 11. The method of claim 10,
The method is
When it is possible to call two or more API servers that provide the same microservice according to a query received from the client, based on at least one of the performance and failure of each of the two or more API servers, The method of operating a gateway device, characterized in that it further comprises a load balancing step of setting a weight so that the two or more API servers are called according to the set weight. 11. The method of claim 10,
The method is
A token is issued to the client by performing authentication based on the authentication information received from the client, and API for a query from the client only when the token issued from the client transmitting the query is confirmed The method of operating a gateway device, characterized in that it further comprises a security processing step of authorizing the call of the server (Authorization).

Images