CN110781441A - New retail business middle desk based on micro-service framework - Google Patents
New retail business middle desk based on micro-service framework Download PDFInfo
- Publication number
- CN110781441A CN110781441A CN201911406564.4A CN201911406564A CN110781441A CN 110781441 A CN110781441 A CN 110781441A CN 201911406564 A CN201911406564 A CN 201911406564A CN 110781441 A CN110781441 A CN 110781441A
- Authority
- CN
- China
- Prior art keywords
- module
- request
- request information
- service
- function
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/283—Multi-dimensional databases or data warehouses, e.g. MOLAP or ROLAP
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0641—Shopping interfaces
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a new retail business middle station based on a micro-service framework, wherein the business middle station is in signal connection with a database and comprises a root module, a middle layer and a plurality of mutually independent function modules, wherein the root module is in signal connection with each function module respectively, and the root module, the middle layer and the database are in signal connection in sequence; the function module is used for collecting operation information input by a user, generating corresponding first request information according to the operation information and sending the first request information to the root module; the root module is used for receiving and combining the first request information to generate corresponding second request information and sending the second request information to the middle layer; the middle layer is used for receiving the second request information, calling a database according to a preset service processing rule or directly carrying out corresponding processing on the second request information to obtain a request result, and returning the request result to the corresponding function module through the root module. The invention can enhance the lateral expansibility of the station in the service.
Description
Technical Field
The invention relates to the technical field of computer application, in particular to a new retail business middle station based on a micro-service framework.
Background
The service platform comprises a service center station and a database, wherein the service center station is used for providing services for users, calling the database according to the operation information input by the users so as to provide corresponding services for the users, and storing, updating and managing the data in the database.
In a traditional business mode, a business middle desk is generally designed in a thick layered mode, the technology is divided into two layers, namely a front-end page and a background interface according to business functions, as shown in fig. 1, all page resources are requested to a background service through REST API (representational state transfer application program) in a unified manner, and all function modules belong to a front-end project, so that each function module in a business scene has strong coupling; in the prior art, if a certain function module is added, changed or deleted, other related function modules are necessarily influenced, the operation and deployment of the whole project are also influenced, and the risk of project errors is increased; the above conventional service middleboxes have the following drawbacks:
(1) the coupling degree between the function modules is too high, independent deployment cannot be realized, and the change of each function module influences other function modules;
(2) interface management consumption is too large, each functional module can only request a specified interface, and data cannot be reused across modules;
(3) the horizontal expansibility is poor, and the normal operation of other function modules can be influenced when one function module is added;
(4) the rendering performance is poor, and the volume of front-end resources is large after uniform packaging, so that the page loading time is too long, and the interaction experience is poor;
(5) background data is poor in reusability, and common data fragments cannot be multiplexed;
(6) the operation and maintenance cost is high, the whole system is likely to be crashed due to online release of any function module, and more operation and maintenance cost is consumed;
and the new retail business center has the characteristics of frequent change of demand, more users, rapid update iteration and the like, but the defects of low flexibility, high deployment and maintenance cost and the like of the traditional business center limit the development of the new retail business, so the prior art needs to be further improved.
Disclosure of Invention
Aiming at the defects in the prior art, the invention provides a novel retail business platform based on a micro-service architecture.
In order to solve the technical problem, the invention is solved by the following technical scheme:
a new retail business center station based on a micro-service architecture is provided, wherein the business center station is in signal connection with a database;
the business middle desk comprises a root module, a middle layer and a plurality of mutually independent function modules, wherein the root module is respectively in signal connection with each function module, and the root module, the middle layer and the database are in signal connection in sequence;
the function module is used for realizing a service function or providing a technology stack;
the root module is used for carrying out module registration on each function module, and the function module after registration is used for collecting operation information input by a user, generating corresponding first request information according to the operation information and sending the first request information to the root module;
the root module is also used for receiving and combining the first request information to generate corresponding second request information, and sending the second request information to the middle layer;
the middle layer is used for receiving the second request information, calling the database according to a preset service processing rule or directly carrying out corresponding processing on the second request information to obtain a request result, and returning the request result to the corresponding function module through the root module.
As an implementable embodiment:
the middle layer comprises a distribution unit and a plurality of service units, and the distribution unit is in signal connection with the service units; the root module comprises an interface request client and a registration unit, the interface request client is respectively in signal connection with each function module and the distribution unit, and the interface request client is used for providing interface request objects corresponding to the service units one by one and providing access entries;
the interface request client combines the first request information with a corresponding interface request object to generate second request information, and sends the second request information to the distribution unit through the access entrance;
the distribution unit distributes the second request information to a corresponding service unit according to an interface request object in the second request information;
and the service unit receives the second request information, analyzes and processes the second request information, obtains a corresponding request result, and returns the request result to the corresponding function module through the distribution unit and the interface request client.
As an implementable embodiment:
the access entry adopts a '/graphql' entry.
As an implementable embodiment:
the registration unit is in signal connection with each function module and is used for acquiring registration information of the function modules and performing module registration on the corresponding function modules according to the registration information, and the function modules after registration provide corresponding functions for users.
As an implementable embodiment:
the registration information at least comprises the name of the corresponding function module, a static file service address, a data warehouse address and a local development project agent address.
As an implementable embodiment:
the registration unit is also used for acquiring the static file of the corresponding function module according to the static file service address and rendering the page according to the static file.
As an implementable embodiment:
the root module also comprises an event distribution unit, the event distribution unit is in signal connection with each function module, and the function modules are communicated through the event distribution unit.
As an implementable embodiment:
the root module further comprises a public dependence unit, the public dependence unit is in signal connection with each function module respectively, and the function modules refer to the third party class library through the public dependence unit.
Due to the adoption of the technical scheme, the invention has the remarkable technical effects that:
1. according to the invention, a traditional business project is divided into a plurality of mutually independent function modules, so that each function module can be independently developed, deployed, released and iterated according to actual conditions;
2. according to the design of the interface request client, on one hand, a uniform access entrance is provided, the problem of excessive interface management consumption in the prior art is solved, and on the other hand, an interface request object is provided, so that requests provided by various functional modules can be distributed to a specified service unit for processing;
3. the interface requests the client to provide a 'or graph ql' entry as an access entry, and the format of returned data can be set based on the graph QL characteristic, so that useless data is filtered;
4. according to the invention, the design of the registration unit can proxy each function module, and the page rendering is realized by acquiring the static file of the function module, so that the problems of slow page loading and poor interaction experience in the prior art when the uniform packaging is performed for rendering are solved;
5. according to the invention, the event distribution unit is designed, so that data can be shared among all the function modules, and the data reuse rate is improved;
6. the design of the public dependency unit can reduce the repeated loading performance consumption of the third-party class library.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a schematic diagram of a business platform architecture in the prior art;
FIG. 2 is a schematic diagram of module connections of a new retail business center based on a micro-servitization architecture according to the present invention;
FIG. 3 is a schematic diagram of a platform architecture in a business in case;
in the figure, 100 is a function module, 200 is a root module, 210 is an interface request client, 220 is a registration unit, 230 is a common dependency unit, 240 is an event distribution unit, 300 is a middle layer, 310 is a distribution unit, and 320 is a service unit.
Detailed Description
The present invention will be described in further detail with reference to examples, which are illustrative of the present invention and are not to be construed as being limited thereto.
Embodiment 1, a new retail business center based on a micro-service architecture, the business center is connected with a database through signals, as shown in fig. 2, the business center includes a root module 200, an intermediate layer 300, and a plurality of function modules 100 which are independent from each other and have specific functions, wherein the root module 200 is connected with each function module 100 through signals, and the root module 200, the intermediate layer 300 and the database are sequentially connected through signals;
the root module 200 is configured to perform module registration on each function module 100, and the function module 100 after registration is configured to collect operation information input by a user, generate corresponding first request information according to the operation information, and send the first request information to the root module 200;
the root module 200 is further configured to receive and combine the first request information to generate corresponding second request information, and send the second request information to the middle layer 300;
the middle layer 300 is configured to receive the second request information, call the database according to a preset service processing rule or directly perform corresponding processing on the second request information, obtain a request result, and return the request result to the corresponding function module 100 through the root module 200.
The function of the function module 100 is single and fixed, and may be a module with a specific service function (such as a login module) or a module with a specific independent technology stack (such as a module using VUE language), as can be seen from the above, in this embodiment, a traditional service project is split into a plurality of mutually independent function modules 100, and each function module 100 can be independently developed, deployed, released and iterated according to actual conditions;
because each function module 100 is deployed alone, each function module 100 independently performs CDN optimization, static resource request time is reduced, and because each function module 100 is developed, released and iterated alone, the development progress of other function modules 100 cannot be relied on, development efficiency can be greatly improved, each function module 100 is equivalent to a black box, when an exception occurs, the whole business project cannot be collapsed, and the abnormal risk of the whole project is reduced.
Note that, a person skilled in the relevant art can develop and deploy the corresponding function module 100 according to the actual needs thereof, so that the specific functions of the function module 100 need not be limited.
In this embodiment, deployment, release, and iteration of each function module 100 are realized by a Docker. Docker is an open source application container engine, which enables developers to pack their applications and dependencies into a portable container, and then to distribute the container to any popular Linux machine, and also can implement virtualization.
Further:
the middle layer 300 comprises a distribution unit 310 and a plurality of service units 320, wherein the distribution unit 310 is in signal connection with the plurality of service units 320; the root module 200 comprises an interface request client 210 and a registration unit 220, wherein the interface request client 210 is respectively connected with each function module 100 and the distribution unit 310 through signals, and the interface request client 210 is used for providing interface request objects corresponding to the service units 320 one by one and providing access entries;
the interface request client 210 combines the first request information with the corresponding interface request object to generate second request information, and sends the second request information to the distribution unit 310 through the access entry;
the distributing unit 310 distributes the second request information to the corresponding service unit 320 according to the interface request object in the second request information;
the service unit 320 receives the second request information and analyzes the second request information to obtain a corresponding request result, and returns the request result to the corresponding function module 100 through the distribution unit 310 and the interface request client 210.
In this embodiment, the interface request Client 210 is an Apollo Client based on GraphQL, and in actual use, an interface request object is pre-established and a corresponding interface service address is configured for the interface request object; the unified interface provided by the interface request client 210 is a 'GraphQL' interface provided by the GraphQL language standard, and based on the characteristics of the GraphQL, the interface request client 210 can specify the data format of the request return and can filter useless data;
such as: the user makes a request for viewing the commodity information through the function module 100, at this time, the commodity module generates first request information according to the operation information of the user and sends the first request information to the interface request client 210, the interface request client 210 generates second request information by combining with a corresponding interface request object, and sends the second request information to the distribution unit 310 through the access entry.
The distribution unit 310 sends the second request information to the service unit 320 with the function of checking the commodity according to the interface request object, the service unit 320 calls a database according to a preset business processing rule, the commodity information of the corresponding commodity is inquired in the database according to the second request information, the inquiry result is sent to the distribution unit 310, and the distribution unit 310 returns to the commodity module through the interface request module.
Assuming that a commodity includes fields of id, name, price, type, weight, skiid, scope, company, etc., all data is returned when a request for viewing commodity information is made in the prior art, regardless of whether the page needs to be displayed or not. In this embodiment, the fields returned by the access entry are restricted, for example, only id, name, and price fields are returned, thereby reducing the requests of useless fields and greatly saving the resource utilization efficiency.
In this embodiment, the interface request client 210 implements an accurate request through an interface request object, such as: when the function module 100 is a login module, configured to provide a user login function, and when a user inputs a user name and a password and confirms login, the login module acquires user operation information to generate first request information, which is used to request authentication of the user name and the password.
Meanwhile, the login module calls the interface request client 210, the interface request client 210 extracts an interface request object pointing to the corresponding service unit 320 according to the first request information, and at this time, the interface request client 210 sends the first request information and the interface request object (i.e., the second request information) to the distribution unit 310 through the access entry.
The distributing unit 310 distributes the second request information to the service unit 320 functioning as a login service according to the interface request object, the service unit 320 calls a database according to the service processing rule, verifies the user name and the password in the second request information, and when the verification is successful, the service unit 320 returns the request result of successful login.
As can be seen from the above, it is not necessary to configure the address of the corresponding service unit 320 for each function module 100, each function module 100 can directly make a corresponding request to the middle layer 300 through the interface request client 210, and the middle layer 300 will distribute the second request information to the service unit 320 with the corresponding function according to the interface request object for processing.
The middle layer 300 (particularly the node middle layer 300, also referred to as a BFF layer) of this embodiment is divided into a plurality of functional interfaces providing specific data resources according to functions, and the interface request object is directed to the functional interfaces; when the middle layer 300 receives the second request information, the second request information is distributed through the Schema provided by the middle layer 300, and a corresponding request result is returned, that is, the distribution unit 310 of the middle layer 300 distributes the second request information, and is further configured to return the request result obtained by processing by the service unit 320 through the interface request client 210, and the service unit 320 is configured to perform parsing processing on the second request information to implement a corresponding function.
Those skilled in the relevant art can set the service processing rule of the service unit 320 according to actual needs, so that each service unit 320 performs parsing processing according to the service processing rule thereof according to the second request information.
Further: the registration unit 220 is connected to each function module 100 for obtaining the registration information of the function module 100, and performing module registration on the corresponding function module 100 according to the registration information, and the function module 100 after registration provides corresponding functions for the user.
That is, each function module 100 needs to be put into use after registration is completed in the root module 200, on one hand, the root module 200 can call the corresponding function module 100 conveniently, on the other hand, the function modules 100 can be added at any time according to actual needs, and the method is flexibly applicable to the characteristic that the requirements of the current new retail business are frequently changed.
Further: the registration information at least includes a name of the corresponding function module 100, a static file service address, a data warehouse address, and a local development project agent address.
Furthermore, the registering unit 220 is further configured to obtain a static file of the corresponding function module according to the static file service address, and render a page according to the static file.
As can be seen from the above, in this embodiment, each function module 100 provides a static file service proxy function to the root module 200, and when a user has an interaction behavior, the root module 200 is triggered to invoke a proxy service of a sub-module, and the sub-module returns a corresponding static file, a data warehouse, and the like.
The method specifically comprises the following steps:
the root module 200 is configured to mount a static file provided by the function module 100 in a browser for operation, and in this embodiment, the registration unit 220 mounts a static file service address of each function module 100 in a browser window.
If the user enters the login page after inputting the address, at this time, the registration unit 220 obtains the static file of the login module through the static file service address provided when the login module registers, and performs page rendering according to the static file, thereby displaying the login page for the user.
As can be seen from the above, the registration unit 220 obtains the static file of the corresponding function module 100 for page rendering when the user enters a certain function module, and compared with the prior art that all function modules 100 are packed for rendering, the problem that the page loading time is too long and the interaction experience is poor due to the large volume of the uniformly packed resources is solved.
Further, the root module 200 further includes an event distributing unit 240, the event distributing unit 240 is in signal connection with each function module 100, and the function modules 100 communicate with each other through the event distributing unit 240.
When the role units need to communicate with each other, the event distribution unit 240 (GlobalEventDistributor) sends corresponding communication data to the event subscriber in an event callback manner, so that event distribution and data interaction are performed between the two role units.
For example, the function module 100 includes a login module and a goods module, wherein the goods module is used for displaying goods for the client;
when the user inputs the user name and the password through the login module to log in and the login is successful, the login module receives the request result that the distribution unit 310 requests the client 210 to return the login success through the interface, and at this time, the login module calls the event distribution unit 240 to send the information of successful login and the user information (such as the user name) of the user out and automatically enter the commodity module.
At this time, the registration unit 220 obtains the static file of the commodity module to perform page rendering, and at the same time, the commodity module obtains the user information shared by the login module through the event distribution unit 240, so that data sharing between the function modules 100 is realized.
As can be seen from the above, the event distribution unit 240 in the present embodiment realizes the sharing of data between the function modules 100, and compared with the prior art, the function modules 100 in the present embodiment do not need to retrieve common data fragments from the database, thereby improving the reusability of such data.
Further, the root module 200 further includes a public dependency unit 230, the public dependency unit 230 is respectively connected to the function modules 100, and the function modules 100 refer to the third party class library through the public dependency unit 230.
In the prior art, each function module 100 loads a third party class library required by the function module 100, but if the mobx state management library is used, each function module 100 is used, and in the prior art, each function module 100 needs to be introduced once, which causes performance waste.
As can be seen from the above, in the embodiment, the third party class library only needs to be loaded once in the public dependency unit 230, and each function module 100 can use the required third party class library through the public dependency unit 230, so as to reduce the repeated loading performance consumption of the third party class library.
Note that in this embodiment, the common dependency unit, the interface request client 210, and the event distribution unit 240 may be packaged into a static javascript file, and inserted into the browser BOM in a script form, so that each function module 100 may be called through a global object.
As shown in fig. 3, a detailed description is given in a specific case:
the function module 100 is deployed, each function module 100 sends registration information to the registration unit 220 for registration, and the function module 100 includes a login module, a commodity module and a navigation module, wherein:
the login module is mainly used for login authentication and other functions and is also an entrance for user interaction.
The commodity module is used for displaying commodities for users and providing functions of checking, editing, adding and deleting commodities for the users.
The navigation module is a navigation entry of the business project, provides the route configuration and the name display of each function module 100, and in this case, the navigation module is shown at the top of the WEB end in the form of Menu.
When the user inputs an address to enter the login page, the registration unit 220 will go to the proxy service of the login module according to the registration information of the sub-module to obtain a static file, and then render the static file to the page to display the login page for the user, at this moment, the login module starts the life cycle of the microservice.
When a user inputs a user name and a password on a login page and confirms login, a login module acquires user operation information to generate first request information for requesting login authentication.
The login module calls the interface request client 210, the interface request client 210 extracts an interface request object pointing to the corresponding service unit 320 according to the first request information, and at this time, the interface request client 210 sends the first request information and the interface request object (i.e., the second request information) to the distribution unit 310 through the access entry. The distributing unit 310 distributes the second request information to the service unit 320 functioning as a login service according to the interface request object, the service unit 320 calls a database according to the service processing rule, verifies the user name and the password in the second request information, and when the verification is successful, the service unit 320 returns the request result of successful login.
In actual use, the service unit 320 may be configured according to actual needs, and as shown in fig. 3, the function of the service unit 320 may be to provide login service, commodity service, order service, authentication service, and the like corresponding to the function module 100, and may also be to provide caching service, data service, middleware service, exception service, interceptor service, and the like according to actual needs.
The distributing unit 310 returns the successful login request result to the login module through the interface request client 210, at this time, the login module navigates to a preset function module 100, such as a commodity module, according to the request result, and the login module invokes the event distributing unit 240 to send the successful login request result and the user information (such as a user name) of the user;
the login module ends the micro-service life cycle of the commodity module, and simultaneously the commodity module starts the micro-service life cycle of the commodity module;
the registration module obtains a static file rendering page according to the registration information of the commodity module, at this time, the page is displayed as a commodity page, and meanwhile, the commodity module event distribution unit 240 obtains user information, so that data sharing among the function modules 100 is realized.
When the commodity module causes page collapse due to abnormal reasons, the login module, the navigation module and the like can also provide services normally, but the whole service is not collapsed abnormally. The decoupling and independent operation between the functional modules 100 greatly reduces the risk of anomalies throughout the project.
When the new retail business changes and an order module is newly added, the new retail business can be used only by deploying the order module and performing module registration on the order module;
after the commodity module is deleted, the user can directly navigate to the order module after login is completed, and at the moment, the user only needs to replace the address for navigation after login of the login module is successful with the order module, so that the deletion of the commodity module can not affect other function modules 100, and development cost is greatly reduced.
The embodiments in this specification are described in a progressive manner.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing terminal to cause a series of operational steps to be performed on the computer or other programmable terminal to produce a computer implemented process such that the instructions which execute on the computer or other programmable terminal provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It should be noted that:
reference in the specification to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the invention. Thus, the appearances of the phrase "one embodiment" or "an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
In addition, it should be noted that the specific embodiments described in the present specification may differ in the shape of the components, the names of the components, and the like. All equivalent or simple changes of the structure, the characteristics and the principle of the invention which are described in the patent conception of the invention are included in the protection scope of the patent of the invention. Various modifications, additions and substitutions for the specific embodiments described may be made by those skilled in the art without departing from the scope of the invention as defined in the accompanying claims.
Claims (8)
1. A new retail business center station based on a micro-service architecture, wherein the business center station is in signal connection with a database, and the new retail business center station is characterized in that:
the business middle desk comprises a root module, a middle layer and a plurality of mutually independent function modules, wherein the root module is respectively in signal connection with each function module, and the root module, the middle layer and the database are in signal connection in sequence;
the function module is used for realizing a service function or providing a technology stack;
the root module is used for carrying out module registration on each function module, and the function module after registration is used for collecting operation information input by a user, generating corresponding first request information according to the operation information and sending the first request information to the root module;
the root module is also used for receiving and combining the first request information to generate corresponding second request information, and sending the second request information to the middle layer;
the middle layer is used for receiving the second request information, calling the database according to a preset service processing rule or directly carrying out corresponding processing on the second request information to obtain a request result, and returning the request result to the corresponding function module through the root module.
2. The microservices-based architecture new retail business kiosk of claim 1 wherein:
the middle layer comprises a distribution unit and a plurality of service units, and the distribution unit is in signal connection with the service units; the root module comprises an interface request client and a registration unit, the interface request client is respectively in signal connection with each function module and the distribution unit, and the interface request client is used for providing interface request objects corresponding to the service units one by one and providing access entries;
the interface request client combines the first request information with a corresponding interface request object to generate second request information, and sends the second request information to the distribution unit through the access entrance;
the distribution unit distributes the second request information to a corresponding service unit according to an interface request object in the second request information;
and the service unit receives the second request information, analyzes and processes the second request information, obtains a corresponding request result, and returns the request result to the corresponding function module through the distribution unit and the interface request client.
3. The microservices-based architecture new retail business kiosk of claim 2 wherein:
the access entry adopts a '/graphql' entry.
4. The microservices-based architecture new retail business kiosk of claim 2 wherein:
the registration unit is in signal connection with each function module and is used for acquiring registration information of the function modules and performing module registration on the corresponding function modules according to the registration information, and the function modules after registration provide corresponding functions for users.
5. The microservices-based architecture new retail business staging of claim 4 wherein:
the registration information at least comprises the name of the corresponding function module, a static file service address, a data warehouse address and a local development project agent address.
6. The microservices-based architecture new retail business staging of claim 5 wherein:
the registration unit is also used for acquiring the static file of the corresponding function module according to the static file service address and rendering the page according to the static file.
7. The microservices-based architecture new retail business kiosk of claim 1 wherein:
the root module also comprises an event distribution unit, the event distribution unit is in signal connection with each function module, and the function modules are communicated through the event distribution unit.
8. The microservices-based architecture new retail business kiosk of claim 1 wherein:
the root module further comprises a public dependence unit, the public dependence unit is in signal connection with each function module respectively, and the function modules refer to the third party class library through the public dependence unit.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911406564.4A CN110781441A (en) | 2019-12-31 | 2019-12-31 | New retail business middle desk based on micro-service framework |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911406564.4A CN110781441A (en) | 2019-12-31 | 2019-12-31 | New retail business middle desk based on micro-service framework |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110781441A true CN110781441A (en) | 2020-02-11 |
Family
ID=69394788
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911406564.4A Pending CN110781441A (en) | 2019-12-31 | 2019-12-31 | New retail business middle desk based on micro-service framework |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110781441A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112363854A (en) * | 2020-11-11 | 2021-02-12 | 南京莱斯信息技术股份有限公司 | Front-end service framework optimization design method based on novel interface standard |
| CN112416308A (en) * | 2020-11-30 | 2021-02-26 | 上海汽车集团股份有限公司 | Software optimization method and device and software architecture |
| CN114020309A (en) * | 2021-11-02 | 2022-02-08 | 爱集微咨询(厦门)有限公司 | Method, device and storage medium for constructing multi-page application through webpack |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106686094A (en) * | 2016-12-30 | 2017-05-17 | 郑州云海信息技术有限公司 | Micro-service architecture |
| CN108418862A (en) * | 2018-01-31 | 2018-08-17 | 金蝶软件（中国）有限公司 | Micro services management method and system based on artificial intelligence service cloud platform |
| CN110138741A (en) * | 2019-04-15 | 2019-08-16 | 平安科技（深圳）有限公司 | Micro services management method, device and computer equipment based on management platform |
-
2019
- 2019-12-31 CN CN201911406564.4A patent/CN110781441A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106686094A (en) * | 2016-12-30 | 2017-05-17 | 郑州云海信息技术有限公司 | Micro-service architecture |
| CN108418862A (en) * | 2018-01-31 | 2018-08-17 | 金蝶软件（中国）有限公司 | Micro services management method and system based on artificial intelligence service cloud platform |
| CN110138741A (en) * | 2019-04-15 | 2019-08-16 | 平安科技（深圳）有限公司 | Micro services management method, device and computer equipment based on management platform |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112363854A (en) * | 2020-11-11 | 2021-02-12 | 南京莱斯信息技术股份有限公司 | Front-end service framework optimization design method based on novel interface standard |
| CN112363854B (en) * | 2020-11-11 | 2023-11-21 | 南京莱斯信息技术股份有限公司 | Front-end service framework optimization design method based on novel interface standard |
| CN112416308A (en) * | 2020-11-30 | 2021-02-26 | 上海汽车集团股份有限公司 | Software optimization method and device and software architecture |
| CN112416308B (en) * | 2020-11-30 | 2024-08-09 | 上海汽车集团股份有限公司 | Software optimization method and device and software architecture |
| CN114020309A (en) * | 2021-11-02 | 2022-02-08 | 爱集微咨询(厦门)有限公司 | Method, device and storage medium for constructing multi-page application through webpack |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108667925B (en) | Method and system for seamless access of WEB application to distributed system | |
| US20160150046A1 (en) | Re-establishing push notification channels via user identifiers | |
| CN110727653B (en) | Multi-project load balancing method and device | |
| CN110781441A (en) | New retail business middle desk based on micro-service framework | |
| US10120886B2 (en) | Database integration of originally decoupled components | |
| CN110784498B (en) | Personalized data disaster tolerance method and device | |
| US10970141B2 (en) | Integrating transaction processing system interfaces with event-driven polyglot runtime modules | |
| US20180131605A1 (en) | Floating internet protocol for private networks | |
| US20130339488A1 (en) | Enterprise services framework for mobile devices | |
| CN112579319A (en) | Service calling method and device based on LRU Cache optimization | |
| CN110750780A (en) | User role permission fusion method, device and equipment based on multi-service system | |
| CN114218619A (en) | Data security protection method, device, medium and electronic equipment | |
| CN113282589A (en) | Data acquisition method and device | |
| CN112698930A (en) | Method, device, equipment and medium for obtaining server identification | |
| CN117435569A (en) | Dynamic capacity expansion method, device, equipment, medium and program product for cache system | |
| CN113535227B (en) | Deployment method and device of digital technology architecture | |
| CN111008202A (en) | Distributed transaction processing method and framework | |
| US10701009B1 (en) | Message exchange filtering | |
| US20140172955A1 (en) | Distributed mobile enterprise application platform | |
| US20110029856A1 (en) | Extensible Web Context in Web Containers | |
| CN115277610B (en) | Message split sending method, device, equipment and medium based on dual-activity environment | |
| CN115484149B (en) | Network switching method, network switching device, electronic equipment and storage medium | |
| CN111782242B (en) | Client dynamic publishing method and device in cloud environment | |
| CN114363172B (en) | Decoupling management method, device, equipment and medium for container group | |
| US20230246916A1 (en) | Service map conversion with preserved historical information |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200211 |