KR101996840B1 - Microservice store operating system - Google Patents

Abstract

The present invention relates to a microservice store operating server for operating a microservice store for selling microservices; A developer terminal for accessing the microservice store operating server through a network to register the microservice developed by the developer as a product in the microservice store; A purchaser terminal connected to the microservice store operating server through the network to search for the microservice sold in the microservice store and purchase the microservice; When a developer registers the microservice in the microservice store and gives the buyer the right to revise the source and the right to distribute or resell the microservice, the developer accesses the microservice store operating server through the network to purchase An organizer terminal for modifying a micro service and registering the modified micro service as a product in the micro service store; And a curator terminal for developing a new application by combining a plurality of micro services purchased by connecting to the micro service store operating server through the network and registering the developed application in the micro service store and selling the developed application, The micro-service store provides a community module that provides communication channels to buyers, developers, developers, and curators. The micro-services that are registered by the developers are cataloged by the curator and registered as a catalog service. Catalogs, and buyers can pay for their catalogs using the payment platform, acquire license rights, install products in their cluster operating environment, and use the services. A microservice application store module that guarantees usage rights of copyright owners and purchasers by providing usage authentication functions, a microservice repository that freely registers microservices created by developers and provides copyright and configuration management functions for services, Module, a local service, a micro service SDK module that provides developers with the ability to develop and test micro services, and register catalog services in the form of a Web UI, provides a payment interface for purchase, And a payment module for providing various payment means interlocking functions through PG interworking.
The microservice store operating system according to the present invention is advantageous in terms of schedule and cost, and has an advantage of being able to easily use microservices.

Description

[0001] Microservice store operating system [0002]

The present invention relates to a microservice store operating system, and more particularly, to a microservice store operating system that is advantageous in terms of schedule and cost and can easily utilize microservices.

Recently, as the introduction of micro service architecture, a software development method, has been developed, S / W development method has changed from developing one huge and complex monolithic to assembling micro services that provide independent functions like LEGO BLOCK have. Micro services are much simpler in size and functionality than LEGO blocks compared to existing complex software structures and can be easily combined with each other, making development fast and easy to maintain.

Although the micro-service architecture provides the advantage of making S / W development easier, there are significant constraints to fully enjoy the benefits. There are not enough micro-services available right away. Currently, each company has its own microservice to use internally, but there is not enough personnel to develop microservice compared to the demand in the organization, and it is not receiving the desired schedule and cost.

Since self-development of micro-services in the enterprise is not smooth, micro-services should be provided outside the organization. Since micro services such as Lego blocks can be used in various cases once they are created, purchasing from outside is advantageous in terms of schedule and cost rather than making necessary micro services directly. Currently, however, there is no provision for an easy-to-find environment for micro-services such as LEGO BLOCK.

Accordingly, the present invention intends to construct and operate a micro service store to activate the micro services required by the software market.

Korean Registered Patent No. 10-1885586 (Registered on July 31, 2018)

SUMMARY OF THE INVENTION Accordingly, the present invention has been made keeping in mind the above problems occurring in the prior art, and it is an object of the present invention to provide a micro service store operating system which is advantageous in terms of schedule and cost and can easily use micro services.

However, the technical problems of the present invention are not limited to the above-mentioned problems, and other technical problems which are not mentioned can be clearly understood by those skilled in the art from the following description.

A microservice store operating system according to an embodiment of the present invention includes a microservice store operating server for operating a microservice store for selling microservices; A developer terminal for accessing the microservice store operating server through a network to register the microservice developed by the developer as a product in the microservice store; A purchaser terminal connected to the microservice store operating server through the network to search for the microservice sold in the microservice store and purchase the microservice; When a developer registers the microservice in the microservice store and gives the buyer the right to revise the source and the right to distribute or resell the microservice, the developer accesses the microservice store operating server through the network to purchase An organizer terminal for modifying a micro service and registering the modified micro service as a product in the micro service store; And a curator terminal for developing a new application by combining a plurality of micro services purchased by connecting to the micro service store operating server through the network and registering the developed application in the micro service store and selling the developed application, The micro-service store provides a community module that provides communication channels to buyers, developers, developers, and curators. The micro-services that are registered by the developers are cataloged by the curator and registered as a catalog service. Catalogs, and buyers can pay for their catalogs using the payment platform, acquire license rights, install products in their cluster operating environment, and use the services. A microservice application store module that guarantees usage rights of copyright owners and purchasers by providing usage authentication functions, a microservice repository that freely registers microservices created by developers and provides copyright and configuration management functions for services, Module, and a micro-service SDK module that provides a function to allow a developer to develop and test a micro-service in the form of a Web UI and register a catalog service, a payment interface for purchasing, and a block chain-based encryption currency And a payment module for providing various payment means interlocking functions through PG interlocking.

The community module supports the openID, OAuth 2.0, LDAP, and social login universal ID authentication schemes, issues and manages subscriber credentials, provides issue tracking and real-time communication channels, and manages the registration and management of media contents. can do.

The micro-service app store module includes a micro-service-specific meta data generation management module, micro-service information and curation management module, a user behavior analysis-based rating management module, a distributed ledger-based license registration and authentication module and a smart contract management module, It is based on PKI for e-wallet. It can be used for various purposes such as product recommendation, product lifecycle management (creation / change / operation / disposal), store usage statistics, marketing data analysis, search, event, promotion information management, The user can take charge of the private key authentication.

The micro-service app store module provides functions related to menu, product composition, and promotion for exposing the micro-services edited by the curator to the store, and the buyers access the catalog service menu, Environment can be supported.

The microservice repository module includes a connection token issuance management, an external authentication I / F linkage, an OCI standard container image registry (Push / pull), a micro service change information management, a container meta information management, Replication, DR management, image scanning, security vulnerability analysis, and automatic cluster installation interface.

The microservice repository module manages the image and meta information of the individual containers constituting the microservice, checks the copyright information and the security weakness to guarantee the integrity of the original image, And to transmit the corresponding image.

The micro service SDK module can perform micro service resource management and container orchestration, register a container application, allocate CPU, memory resource allocation, service open, storage, and automate the container build configuration.

The micro-service SDK module can provision and manage multi-clusters, catalog and organize the micro-services in the store, manage the micro-services dynamically, and manage the micro-services.

The micro-service SDK module can integrate the application infrastructure, monitor the micro-service status information and the cluster infrastructure information, and link the micro-service store password.

The payment module may provide a settlement request, a transaction history check, and a settlement history inquiry function using an I / F of a network that is a chain of a CST (Cloud Service Token) payment block.

The microservice store operating system according to the present invention is advantageous in terms of schedule and cost, and has an effect of being able to use microservices easily.

1 is a block diagram of a microservice store operating system according to an embodiment of the present invention.
2 is a diagram illustrating a system for configuring a microservice store according to one embodiment of the present invention.
3 through 5 are flowcharts illustrating a method of operating a microservice store according to an embodiment of the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS The advantages and features of the present invention and methods of achieving them will become apparent with reference to the embodiments described in detail below with reference to the accompanying drawings. It should be understood, however, that the invention is not limited to the disclosed embodiments, but may be embodied in many other forms and should not be construed as being limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Is provided to fully convey the scope of the invention to those skilled in the art, and the present invention is only defined by the claims.

Like reference numerals refer to like elements throughout the specification.

Hereinafter, a microservice store operating system according to an embodiment of the present invention will be described with reference to the accompanying drawings.

It will be appreciated that the combinations of blocks and flowchart illustrations in the process flow diagrams may be performed by computer program instructions.

These computer program instructions may be loaded into a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, so that those instructions, which are executed through a processor of a computer or other programmable data processing apparatus, Thereby creating means for performing functions.

These computer program instructions may also be stored in a computer usable or computer readable memory capable of directing a computer or other programmable data processing apparatus to implement the functionality in a particular manner so that the computer usable or computer readable memory The instructions stored in the block diagram (s) are also capable of producing manufacturing items containing instruction means for performing the functions described in the flowchart block (s).

The computer program instructions It is also possible to mount on a computer or other programmable data processing equipment, so that a series of operating steps may be performed on a computer or other programmable data processing equipment to create a computer-executed process to perform a computer or other programmable data processing equipment May also provide steps for performing the functions described in the flowchart block (s).

Each block may also represent a portion of a module segment or code that includes one or more executable instructions for executing the specified logical function (s). It should also be noted that in some alternative implementations, the functions mentioned in the blocks may occur out of order. For example, two blocks that are shown one after the other may actually be executed substantially concurrently, or the blocks may sometimes be performed in reverse order according to the corresponding function.

1 is a block diagram of a microservice store operating system according to an embodiment of the present invention.

1, a microservice store operating system according to an embodiment of the present invention includes a microservice store operating server 100, a purchaser terminal 110, a developer terminal 120, an operator terminal 130, And a terminal 140. Here, the microservice store operating server 100, the purchaser terminal 110, the developer terminal 120, the developer terminal 130, and the curator terminal 140 may be interconnected through a wired or wireless network, The mobile terminal 110, the developer terminal 120, the producer terminal 130 and the curator terminal 140 are connected to the microservice store operating server 100 through a network such as a smart phone, a notebook PC, a desktop personal computer It is possible to connect with an electronic device.

The micro-service store operating server 100 is a server 100 for operating a micro-service store to provide micro-services. The server 100 mediates transactions between buyers, developers, developers, and curators, Customer management.

The microservice store operating server 100 downloads and installs a "microservice store" application from the buyer terminal 110, the developer terminal 120, the developer terminal 130 and the curator terminal 140, .

Micro-services consist of source code, metadata, and container images. Therefore, the micro-service store operating server 100 should be provided with a source code repository supporting configuration management, a container image registry environment, and a build environment from source code to images. Because micro-services are built on a container basis, container management tools must be provided to develop, test, and use micro-services. To this end, the microservice store operating server 100 provides a software development kit (SDK). The SDK allows developers to develop and test micro services in a local environment.

The purchaser, the developer, the implementer, and the curator can use the service by joining the micro service store operating server 100 as a member, and the micro service store operating server 100 can store and manage the registered member information in the database .

The microservice store operation server 100 stores and manages an application developed by a developer or an applicant and developed by a curator, in a database. Each of the buyer, developer, developer, and curator can access the microservice store operating server 100 through the terminal and retrieve the microservices and applications stored in the database. Micro service, information on each micro service when searching for an application, number of user installations per application, number of purchases, user evaluation, and user recommendation. Micro services, and applications are registered as a catalog menu for one-click installation and use, allowing buyers to conveniently install them regardless of their operating environment.

The microservice store operating server 100 may form a communication channel between the developer and the buyer, the developer and the developer (or the buyer), the curator and the developer (or the buyer). Through the communication channel, the buyer can make a development request to the developer, and the buyer can ask the developer, the developer or the curator about the product or inquire about how to use the product after purchase, You can ask the developer about the product, or the curator can ask the developer about the product before developing the application.

The developer terminal 120 is a terminal owned by the micro service developer. The developer accesses the micro service store operating server 100 through the developer terminal 120 and registers the micro service developed by the user in the micro service store as a product . Meanwhile, the developer can register his or her development history or field in the profile at the time of membership in the microservice store operating server 100.

When a developer requests micro-service development from the micro-service store operating server 100 through the developer terminal 120, the developer may develop and accept the micro-service through the developer terminal 120 and develop the micro-service. Then, the developer connects the developed micro service to the micro service store operating server 100 and registers the micro service as a product in the micro service store.

Meanwhile, when registering the developed micro-service in the micro-service store operating server 100, the developer reserves the right to modify and distribute the source, or resell the buyer, .

Developers can earn revenue from microservice sales. For example, Developer A has developed a multi-party chat feature while developing past indie games. However, the game is not popular enough to stop the service. However, in the case of the multi-party chat function, it is a function that is required in various games. Therefore, if this function is separated into a micro service form and registered in the micro service store, although the game is stopped, It is possible to recover the expenditure spent on game production.

The developer terminal 130 is a terminal owned by a micro-service developer. When a developer registers a micro-service in a micro-service store, the developer gives the buyer the right to modify the source and the right to distribute or resell the micro- The user can access the microservice store operating server 100 through the authoring terminal 130 to modify the purchased microservice and register the modified microservice as a commodity in the microservice store. At this time, the developer can communicate with the developer or the purchaser through the communication channel of the microservice store operating server 100. It is desirable that the revenue from the sale of the modified micro service at the time of modification of the micro service purchased by the applicant is shared with the first micro service developer before the modification to guarantee the copyright.

For example, video security company A decides to purchase video analytics micro-services to develop the ability to detect intruders from security camera images in a micro-service store. However, in the field of image sensing, it is necessary to constantly modify the source to improve performance. Therefore, a micro service that finds a micro service that entitles the user to modify and distribute rights in the micro service store is discovered and purchased. The video security company A can analyze the source of the purchased micro-service and modify the source structure and configuration information to improve the performance and apply it internally to the product.

In another example, developer B discovers, purchases, installs, and uses object recognition API (application programming interface) services developed by developer A in a microservice store. While the performance of the API service does not meet the service requirements, while you are looking at the source code, you will notice that the performance is more than doubled by modifying some code and changing only the settings. However, knowing that Developer A acknowledges the right to source and resell rights to the Object Recognition API, it has improved the performance of the API and registered the improved product in the Micro Service Store. As sales of new and improved micro services increase, developer B gains revenue from his contribution and also distributes some of the revenue generated to developer A, the original developer.

The curator terminal 140 can be a terminal carried by a micro service curator and the curator can access a micro service store operating server 100 through a curator terminal 140 to combine a plurality of purchased micro services to develop a new application , And the developed application can be registered and sold in microsusstore. At this time, the curator can communicate with the developer or the purchaser through the communication channel of the microservice store operating server 100.

For example, a customer A, a system operator at a customer center, finds a microservice B that extracts text from audio in a microservice store, a microservice C that analyzes emotions in text, and a microservice D that manages data . A knows that in the customer center industry there is a requirement to automatically store textual conversations with customers and to identify unhealthy customer calls. A is not a professional developer, but can combine micro-services B, C, and D with a little development knowledge to create an application E that automatically identifies high-valued conversation content from a customer call record, You can earn money by registering with. In this case, it is also preferable to distribute a part of the sales revenue generated to the first developers B, C, and D developers to guarantee copyright.

As a copyrighted microservice store becomes active, it will provide a viable means for developers to have a sustainable means of revenue, like composers in the music industry. Once a high-quality micro-service has been developed and registered in the store, whenever a sale of an application that uses micro-services or micro-services as its material, as well as revenue from its own sales, improves the micro-service, Part of the proceeds can be paid. This situation is similar to the situation where a songwriter plays a song, the song is remade, or a song is remixed as a material.

The purchaser terminal 110 is a terminal owned by the purchaser. When the purchaser accesses the microservice store operating server 100 through the purchaser terminal 110 to search for the microservice and requests purchase of the microservice, (100) provides the micro-service to the buyer.

For example, an e-commerce company that is developing a mobile app store needs to develop a SMS sending function at the time of shipment to a user. In order to develop such a function, a developer may have to hang for several weeks. On the other hand, the microservice store operating server 100 provides a service that can easily use the SMS sending function by paying only 10,000 won per month. Once A has decided to purchase a micro-service in the micro-service store, taking into account the schedule and costs, the function will be available with a few clicks.

Therefore, internal development can be insufficient for internal developers, there is a lot of development cost, there is a short time until the application after development, and a separate verification is required. Therefore, it can be used immediately after purchasing at low cost, requires only the developer capacity to perform interlocking work, and has a proven function through various customer use examples, so that there is no need for additional verification.

Also, if the purchaser can not access the microservice store operating server 100 through the purchaser terminal 110 to search for the microservices to be purchased, a developer list having a development history in the corresponding field is presented. The micro-service store management server 100 may request the developer to request development of the micro-service. When the development of the corresponding micro service is completed and registered as a product in the micro service store, a message indicating that the corresponding micro service is developed and registered in the purchaser terminal 110 may be sent. Then, the purchaser can access the microservice store operating server 100 through the purchaser terminal 110 and purchase the corresponding microservice.

For example, an e-commerce company A wants to change the MMS sending function to the SMS sending function at the start of delivery. There is no developer in MMS development experience in the company. In order to develop the function, it is necessary to learn about MMS standard. When I looked at the microservice store, I found that there were no micro services related to MMS, but I had a developer who had experience developing MMS. When the company A requests the development of the MMS sending micro-service through the micro-service store operating server 100, the micro-service store operating server 100 requests the corresponding developer terminal 120 to develop the MMS sending micro-service, And accepts it through the terminal 120. The developer develops a micro service having an MMS dispatch function and registers the micro service as a product in the micro service store through the micro service store operating server 100. Company A then purchases the MMS sending micro-service, and other companies can purchase and use it. Meanwhile, when the MMS sending micro-service is registered as a product in the micro service store, a message informing that the product requested for development is registered is sent to the buyer terminal 110 of the company A who requested the development.

The purchaser can access the micro service store operating server 100 to register and inquire the latest service period of the micro service. Depending on the use of micro-services, buyers may consider purchasing.

The microservice purchaser can purchase the digital token issued by the microservice store and purchase the microservice with the purchased digital token. Digital tokens are protected by encryption algorithms, which can protect personal information. The token can be continuously circulated in the microservice store because it guarantees the right to use the microservice.

The Micro Service Store consists of proven, standardized, and reliable technologies that can be delivered as global services and supports open architecture and flexible scalability.

Each system in the microservice store is composed of micro services and is designed to be flexible in accordance with business changes. The configuration system is shown in FIG.

The configuration system of the microservice store includes a community module 200, a microservice application store module 210, a microservice repository module 220, a microservice SDK module 230, a payment module 240, .

The community module 200 is a module for providing a communication channel to a buyer, a developer, an implementer, and a curator, and provides participant authentication and contents management functions. It supports universal ID authentication scheme such as openID, OAuth 2.0, LDAP, and social login, issues and manages subscriber credentials, provides issue tracking, real-time communication channels, and registers and manages media contents.

The community module 200 provides a free communication space between the buyer, the developer, the maker, and the curator to exchange various ideas and technologies to provide an environment in which creativity-rich projects are created. The community module 200 includes user management, authentication, communication management, and media management modules.

The microservice application store module 210 provides the entire functions through a web screen. The curator examines the microservices registered by the developer, registers them as a catalog service, and provides custom catalog catalog services to the buyers. The purchaser can use the service by using the settlement platform to purchase the catalog, install the product in his cluster operating environment after obtaining the license right, manage the license right, provide the use authentication function, .

The microservice application store module 210 includes a microservice-specific metadata generation management module, a microservice information and curation management module, a user behavior analysis-based rating management module, a distributed ledger-based license registration and authentication module and a smart contract management module, (Creation / change / operation / discard), store usage statistics and marketing data analysis, search, event, promotion information management, payment information registration, settlement business transaction function, electronic wallet PKI-based user private key interlock authentication.

The micro-service application store module 210 provides menu, product configuration, and promotion related functions for exposing the micro-services edited by the curator to the store. The buyer accesses the catalog service menu, To the cluster environment. Purchased micro-services are managed through smart contracts to manage license issuance and payment and settlement transactions, ensuring reliable transactions on block-chain networks. The microservice application store module 210 includes a Curation management module, a License management module, a Store management module, and an Order & Payment management module.

The microservice repository module 220 freely registers the microservices generated by the developers and provides copyright and configuration management functions for the services. Micro Service is registered as a container image and supports extensibility by linking with an external container image store.

The microservice repository module 220 is used to manage connection token issuance management, external authentication I / F integration, OCI standard container image registry (Push / pull), micro service change information management, container information management, , image replication, DR management, image scanning, security vulnerability analysis, and automatic cluster installation interface.

The microservice repository module 220 manages the image and meta information of the individual containers constituting the microservice and checks the copyright information and security vulnerabilities to ensure the integrity of the original image. In addition, it provides the function to check the valid authority at the time of the distribution request for micro service installation and to transmit the corresponding image. The microservice repository module 220 includes an image repository, rights management, vulnerability scanning & auditing management, and a deployment management module.

The micro service SDK module 230 is installed in a local environment and provides a function of a developer to develop and test a micro service in the form of a Web UI and to register a catalog service.

The microservice SDK module 230 performs microservice resource management and container orchestration. The Micro Service SDK registers container applications and allocates CPU, memory resource allocation, service open, and storage.

And the Micro Service SDK module 230 automates the container build configuration. In other words, it works with the source repository and automatically builds the container image according to each development language.

The MicroService SDK module 230 provisions and manages multiple clusters. In other words, the clusters are configured in the environment (Public, Private Cloud, baremetal) where the container is to be driven and the cluster management information is entered through the SDK to remotely manage the operation (multiple clusters are managed simultaneously).

The micro service SDK module 230 links the micro service store catalog. In other words, the created micro service is cataloged and registered in the store.

The microservice SDK module 230 dynamically distributes and manages microservices. The buyer purchases paid / free micro-services from the catalog screen in the store and installs them directly into the cluster linked to the SDK.

The Micro Service SDK module 230 provides integrated monitoring of the application infrastructure. And monitors the status information of the micro service and the information of the cluster infrastructure.

The micro-service SDK module 230 links the micro-service store password. Services sold in the store are settled in encrypted e-wallets through a registered electronic wallet.

The micro-service SDK module 230 can develop, test, purchase, and manage the micro-services in the user's local environment to create and test micro-services in various development languages and register the products in the store. In addition, it provides various collaborative environment with the participants in cooperation with the community. The micro-service SDK module 230 includes an authentication, a build management, an app management, a catalog, and a cluster management module.

The payment module 240 provides a payment interface for purchase in the store, and provides various payment means interlocking functions through block chain-based encryption currency and PG interworking. To do this, we provide user account authentication linkage, PG linkage (domestic / overseas credit / check card), and password currency interlocking I / F (own coin, BTC, ETH, EOS etc).

The payment module 240 provides a settlement request, a transaction history check, and a settlement history inquiry function by using an I / F of a chain of a CST (Cloud Service Token) payment block. The payment means module 240 includes a payment request, a transaction query, and a settlement query module.

3 is a flowchart illustrating a method of operating a microservice store according to an embodiment of the present invention.

Referring to FIG. 3, a developer accesses a microservice store operating server 100 through a developer terminal 120 and registers the developed microservice as a commodity in a microservice store (S100).

The purchaser accesses the microservice store operating server 100 through the purchaser terminal 110 to search for registered micro services (S110).

If the desired micro-service is found, the purchaser uses the purchased micro-service (S120, S130).

The microservice store operating server 100 distributes the profit from the sale of the microservice to the developer (S140).

On the other hand, if the micro-service desired by the buyer is not searched, the purchaser can request the development of the developer terminal 120 through the micro-service store operating server 100 (S150).

When the development of the micro-service requested by the developer is completed and registered as a product, the purchaser can purchase the desired micro-service (S160, S130).

4 is a flowchart illustrating a method of operating a microservice store according to an embodiment of the present invention.

Referring to FIG. 4, the author first accesses the microservice store operating server 100 through the organizer terminal 130, and searches for micro services. At this time, the applicant searches for microcontroller licenses, distribution rights or resale rights. Then, the applicant purchases the desired micro-service (S200).

The modifier modifies the purchased micro-service and registers the micro-service as a product in the micro-service store (S210).

The purchaser can purchase and use a modified micro-service registered as a commodity (S220).

The microservice store operating server 100 distributes the revenue of the modified microservice to the developer and the first developer (S230).

5 is a flowchart illustrating a method of operating a microservice store according to an embodiment of the present invention.

Referring to FIG. 5, the curator first accesses the microservice store operating server 100 through the curator terminal 140 to search for a microservice (S300).

The curator develops a new application by combining a plurality of micro-services purchased after purchasing a desired plurality of micro-services (S310, S320).

The curator registers the developed application as a commodity in the microservice store (S320).

The purchaser can purchase and use the application registered as the product (S330).

The microservice store operating server 100 distributes the revenue of the application to the curator and the first microservice developers at step S340.

On the other hand, in most enterprise environments, it is often difficult to use the original application form developed by curators. It is necessary to change the UI (User Interface) according to the enterprise environment or to change the interworking for legacy integration. In this case, the purchaser can access the microservice store operating server 100 through the purchaser terminal 110 and send a request to the curator to modify the microservice part constituting the application (S350).

Then, the curator reviews the application modification request of the purchaser transmitted through the curator terminal 140 (S360).

In some cases, the curator simply solves the application modification request by changing the connection and configuration of the micro-service, and sometimes the source code of the underlying micro-service needs to be modified.

If the curator determines that the first developer does not need the correction, the correction fee is registered in the microservice store operating server 100 and the buyer pays the correction fee (S370, S380). The curator then modifies the application and provides the modified application to the buyer (S390, S400). The microservice store operating server distributes the profit of the correction work to the curator (S410).

If the curator determines that the curator needs to modify the underlying micro-service, and if the curator can not directly modify the micro-service, the micro-service revision review request is sent to the first developer through the micro-service store operating server 100 (S370, S420).

The initial developer reviews the request of the curator delivered to the developer terminal 120 and negotiates the cost with the curator (S430). The curator can pay for the modification cost if the curator agrees with the buyer on the cost of the developer and the curator's work cost and registers with the microservice store operation server 100 after the cost for the application modification is negotiated. On the other hand, the modification cost may be registered in the microservice store operating server 100 in advance.

The first developer develops a customized micro service by modifying the existing micro service, and transmits the customized micro service to the curator through the micro service store operating server 100 (S440).

The curator reconfigures the application using the modified customized microservice (S450).

The buyer receives the modified customized application from the curator through the microservice store operating server 100 and uses the customized application (S460).

The microservice store operating server 100 distributes the work costs related to the application modification work to the curator, and distributes the work costs related to the micro service development work to the developers (S470).

Meanwhile, the S / W contract as in the present invention is different from the general product contract in that the use condition according to the S / W license is required. In the past, uncomfortable tasks such as offline processing and documenting were required in purchasing S / W licenses. Now, however, block-chain smart contract technology has emerged that can be easily contracted in an online environment in virtually all areas where contracting is required. Smart contract technology not only lowers the cost of the contract but also eliminates uncertainty about the terms of use between the provider and the user, smoothly complies with the transaction contract, and prevents problems such as contract failure or dispute. do.

And providing various payment means in the digital economy is one of the main factors that constitute the competitive advantage of electronic commerce. As the block chain economy becomes more active, smart tokens as well as various tokens and encrypted currencies are emerging. Tokens and encrypted money on the block chain provide a more transparent and secure means of payment than traditional credit card payments. Providing tokens and encrypted money as a means of payment in the purchase of micro services will increase the value of the use of the encrypted money, which again can bring about a virtuous cycle of activation of the micro services ecosystem.

Transactions on the microservice store of the present invention are performed through smart contracts and recorded in a block chain to provide stability / transparency / reliability of transactions, and irreversibility of transactions and accurate profit distribution among participants. By providing an environment where each participant can autonomously create a smart contract, it will be able to support various emerging business models, which will eventually lead to the production and utilization of micro services.

The micro-service store environment of the present invention provides an environment in which anyone can easily develop a service and can use the micro-service, and provides a communication channel between a service user and a developer such as a micro-service development request and development acceptance. Provide an environment for registering, exposing and promoting, and provide monetization means to receive compensation for service copyright and usage. In addition, through smart contract technology, contracts for service use are made simple, safe and transparent, and various payment means including encryption money are provided.

As described above, according to the microservice store operating system and method of the present invention, it is advantageous in terms of schedule and cost, and microservice can be easily utilized.

The present invention has been described with reference to preferred embodiments thereof. It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims. Therefore, the disclosed embodiments should be considered in an illustrative rather than a restrictive sense. The scope of the present invention is defined by the appended claims rather than by the foregoing description, and all differences within the scope of equivalents thereof should be construed as being included in the present invention.

100: microservice store operation server 110: buyer terminal
120: Developer terminal 130: Developer terminal
140: Curator terminal

Claims (10)

A microservice store operating server running a microservice store for selling microservices;
A developer terminal for accessing the microservice store operating server through a network to register the microservice developed by the developer as a product in the microservice store;
A purchaser terminal connected to the microservice store operating server through the network to search for the microservice sold in the microservice store and purchase the microservice;
When a developer registers the microservice in the microservice store and gives the buyer the right to revise the source and the right to distribute or resell the microservice, the developer accesses the microservice store operating server through the network to purchase An organizer terminal for modifying a micro service and registering the modified micro service as a product in the micro service store; And
And a curator terminal for developing a new application by combining a plurality of micro services purchased by connecting to the micro service store operating server through the network and registering the developed application in the micro service store and selling the developed application,
The micro-service store provides a community module that provides communication channels to buyers, developers, developers, and curators. The micro-services that are registered by the developers are cataloged by the curator and registered as a catalog service. It provides the catalog curation service. The buyer can use the payment platform to purchase the catalog, acquire the license right, install the product in his cluster operating environment, use the service, manage the license right, A micro service repository module that freely registers micro services created by developers and provides copyright and configuration management functions for the services, It is a micro service SDK module that installs in a curl environment and provides developers with the ability to develop and test micro services, and register catalog services in the form of a Web UI. It also provides a payment interface for purchase, And a payment module for providing various payment means interlocking functions through interlocking.
The method according to claim 1,
The community module supports the openID, OAuth 2.0, LDAP, and social login universal ID authentication schemes, issues and manages subscriber credentials, provides issue tracking, real-time communication channels, and registers and manages media content. A microservice store operating system.
The method according to claim 1,
The micro-service app store module includes a micro-service-specific meta data generation management module, a micro-service information and curation management module, a user behavior analysis based rating management module, a distributed ledger-based license registration module, an authentication and smart contract management module, It is based on PKI for e-wallet. It can be used for various purposes such as product recommendation, product lifecycle management (creation / change / operation / disposal), store usage statistics and marketing data analysis, search, event, promotion information management, A microservice store operating system that handles user private key authentication.
The method of claim 3,
The micro-service app store module provides functions related to menu, product composition, and promotion for exposing the micro-services edited by the curator to the store, and the buyers access the catalog service menu, A microservice store operating system that supports the installation process in the environment.
The method according to claim 1,
The microservice repository module includes a connection token issuance management, an external authentication I / F linkage, an OCI standard container image registry (Push / pull), a micro service change information management, a container meta information management, The Micro Service Store operating system is responsible for replication, DR management, image scanning, security vulnerability analysis, and automatic installation of clusters.
6. The method of claim 5,
The microservice repository module manages the image and meta information of the individual containers constituting the microservice, checks the copyright information and the security weakness to guarantee the integrity of the original image, And provides the function to transmit the corresponding image.
The method according to claim 1,
The Micro Service SDK module is a micro service store operating system that performs micro service resource management and container orchestration, registers a container application, allocates CPU, memory resource allocation, service open, storage, and automates the container build configuration.
8. The method of claim 7,
The micro-service SDK module is a micro-service store operating system for provisioning and managing a multi-cluster, registering and managing micro-services in a catalog, organizing micro-services, and dynamically distributing and managing micro-services.
9. The method of claim 8,
The micro-service SDK module integrates the application infrastructure, monitors the status information of the micro-service and the information of the cluster infrastructure, and links the micro-service store password to the micro-service store operating system.
The method according to claim 1,
The payment module provides a settlement request, a transaction history check, and a settlement history inquiry function using an I / F of a network that is a CST (Cloud Service Token) payment block network.

Images