CN112711396A - Micro-service layered structure supporting flexible expansion - Google Patents
Micro-service layered structure supporting flexible expansion Download PDFInfo
- Publication number
- CN112711396A CN112711396A CN202011497278.6A CN202011497278A CN112711396A CN 112711396 A CN112711396 A CN 112711396A CN 202011497278 A CN202011497278 A CN 202011497278A CN 112711396 A CN112711396 A CN 112711396A
- Authority
- CN
- China
- Prior art keywords
- service
- micro
- layer
- logic
- cluster
- 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
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
- G06F8/24—Object-oriented
-
- 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
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
Abstract
The invention provides a micro-service layered structure supporting flexible extension, which relates to the technical field of software development and comprises the following steps: the application display layer is used for providing service data for at least one terminal application; the business logic layer comprises a case logic micro-service cluster layer and a general logic micro-service cluster layer which are associated with the preset business scene, wherein the case logic micro-service cluster in the case logic micro-service cluster layer realizes the business logic processing of the associated preset business scene by calling the general micro-service cluster in the general logic micro-service cluster layer to obtain the corresponding business data; and the data processing layer comprises at least one data processing micro-service cluster and is used for providing storage read-write service for the service data obtained by the service logic layer. The method has the advantages of conveniently performing elastic expansion of transverse and longitudinal services, simplifying the complexity of calling relations among the micro services, fully exerting the original characteristics of the micro services and effectively avoiding the possible chaotic condition of cross calling among a plurality of micro services.
Description
Technical Field
The invention relates to the technical field of software development, in particular to a micro-service hierarchical structure supporting flexible expansion.
Background
Micro service Architecture (micro service Architecture) is an Architecture concept, which aims to implement decoupling of a solution by decomposing functions into discrete services, i.e., decomposing functions into discrete services, thereby reducing the coupling of a system and providing more flexible service support. Because of its good expandability, flexibility is very favored. However, the micro-service architecture disperses the whole application into a plurality of services, the services need to be coordinated and matched with each other, a final value is provided for a user, although the micro-service architecture has higher flexibility and expansibility, if the application specification of the micro-service architecture is not reasonably planned, a backfeed effect may be brought, for example, problems of long calling link, high complexity, disordered writing and calling, difficult later-stage operation and maintenance and the like are caused.
Disclosure of Invention
To solve the problems existing in the prior art, the present application provides a micro-service layered structure supporting flexible extension, comprising:
the application display layer is used for providing service data for at least one terminal application so that the terminal application can display and operate the service data;
a service logic layer, wherein the service logic layer comprises a case logic micro service cluster layer and a general logic micro service cluster layer which are associated with a preset service scene, and the case logic micro service cluster in the case logic micro service cluster layer realizes the service logic processing of the associated preset service scene by calling the general micro service cluster in the general logic micro service cluster layer to obtain the corresponding service data;
the data processing layer comprises at least one data processing micro-service cluster and is used for providing storage read-write service for the service data obtained by the service logic layer;
the application display layer, the service logic layer and the data processing layer are arranged from top to bottom in a layered mode.
Preferably, the service logic layer includes a micro service gateway interface, and the service logic layer provides the service data to the application presentation layer through the micro service gateway interface.
Preferably, in the service logic layer, the microservice gateway interface, the case logic microservice cluster layer, and the general logic microservice cluster layer are arranged in an up-to-down hierarchy.
Preferably, the service gateway interface implements data interaction with the application presentation layer by using at least one gateway security verification mode.
Preferably, in the service logic layer, a common service logic is abstracted from each of the predetermined service scenes to form at least one common microservice cluster.
Preferably, in the service logic layer, the case micro service cluster inherits the general micro service provided by the corresponding general micro service cluster in an object-oriented manner.
Preferably, each case micro service cluster is deployed with a first load balancing module and a plurality of case micro service nodes, and the first load balancing module performs load balancing distribution according to the working state of each case micro service node.
Preferably, each general microservice cluster is deployed with a second load balancing module and a plurality of general microservice nodes, and the second load balancing module performs load balancing allocation according to the working state of each general microservice node.
Preferably, each data processing microservice cluster is deployed with a third load balancing module and a plurality of data processing microservice nodes, and the third load balancing module performs load balancing distribution according to the working state of each data processing microservice node.
Preferably, each data processing micro-service cluster is also provided with at least one database and an access queue module respectively connected with each data processing micro-service node and the database, and the access queue module realizes the read-write operation of each data processing micro-service node on the database in a queue mode.
Preferably, the case logic service cluster layer, the general logic micro service cluster layer and the data processing layer respectively realize the elastic expansion of the case micro service cluster, the general micro service cluster and the data processing micro service cluster by adopting a containerization technology.
The application also provides a vehicle marketing system, which adopts the micro-service layered structure supporting flexible expansion.
The technical scheme has the following advantages or beneficial effects:
1) the service logic and the data processing are arranged in a layered mode, so that the elastic expansion of transverse traffic is facilitated, the service complexity is expanded longitudinally in an abstract inheritance mode, the multiplexing relation among the micro-services is optimized, the complexity of the calling relation among the micro-services is simplified, the original characteristics of the micro-services can be fully exerted, and the possible disorder condition of cross calling among a plurality of micro-services can be effectively avoided;
2) by setting the micro-service gateway interface, application display and actual service logic processing are effectively separated, the display and operation of the same service on different terminal applications can be supported, and the expansion of various service contacts possibly occurring in subsequent service scenes are facilitated;
3) the micro-service gateway interface ensures the safety of data interaction with the application display layer by adopting various gateway safety check modes, so that the micro-service layered structure has certain safety and robustness;
4) in a data processing layer, a queue mode is adopted to effectively solve the database distributed transaction.
Drawings
FIG. 1 is a diagram illustrating a micro-service hierarchy supporting flexible extensions according to a preferred embodiment of the present application;
fig. 2 is a schematic structural diagram of an application presentation layer and a service logic layer corresponding to a payment service in a preferred embodiment of the present application.
Detailed Description
The invention is described in detail below with reference to the figures and specific embodiments. The present application is not limited to this embodiment, and other embodiments may be included in the scope of the present application as long as they meet the gist of the present application.
The technical means provided below are all examples for realizing the gist of the present application, and it can be understood that, in the case of no conflict, the following embodiments and technical features in the embodiments can be combined with each other. Also, the scope of protection of the present application should not be limited by the examples used to illustrate the feasibility of the present application.
In a preferred embodiment of the present application, based on the above problems in the prior art, there is provided a microservice hierarchical structure supporting flexible extension, as shown in fig. 1, including:
the application display layer 1 is used for providing service data for at least one terminal application 2 so that the terminal application 2 can display and operate the service data;
a service logic layer 3, the service logic layer 3 includes a case logic micro service cluster layer 31 and a general logic micro service cluster layer 32 which are associated with the predetermined service scene, the case logic micro service cluster 311 in the case logic micro service cluster layer 31 realizes the service logic processing of the associated predetermined service scene by calling the general micro service cluster 321 in the general logic micro service cluster layer 32 to obtain the corresponding service data;
the data processing layer 4, the data processing layer 4 includes at least one data processing microservice cluster 41, is used for providing the storage read-write service for the business data that the business logic layer 3 processes and gets;
the application display layer 1, the service logic layer 3 and the data processing layer 4 are arranged from top to bottom in a layered mode.
Specifically, in the embodiment, through the application presentation layer 1, the service logic layer 3, and the data processing layer 4 which are layered from top to bottom, user interaction processing, service logic processing, and data storage read-write can be effectively stripped, thereby facilitating flexible expansion of services and effectively avoiding a possible confusion situation of cross call among multiple micro services. The application display layer 1 is only responsible for user interaction processing and is not responsible for any service logic processing, namely, interaction of service data with the terminal application 2, so that service data is provided for the terminal application 2 to be displayed, and an operation instruction given by the terminal application 2 is received; the service logic layer 3 is responsible for combing specific service logic contents, and realizing service logic processing of a predetermined service scene to obtain corresponding service data for display and operation of the terminal application 2; the data processing layer 4 is responsible for providing storage read-write services of the service data, including but not limited to floor storage and summarization of the service data, query and screening processing of the service data, and other services.
Further, in the service logic layer 3, a layered design is adopted, and the layered design includes a case logic micro service cluster layer 31 and a general logic micro service cluster layer 32, wherein the case logic micro service cluster layer 31 serves as an upper layer directly facing to the outside, and according to a predetermined service scene associated with the case micro service cluster 311, a corresponding general micro service cluster 321 in the general logic micro service cluster layer 32 is called downwards to realize service logic processing of the predetermined service scene, and by abstracting the general micro service cluster 321, the multiplexing relationship between micro services is effectively optimized, and meanwhile, elastic expansion is facilitated. The elastic expansion comprises horizontal and vertical expansion, wherein for the individual case logic micro service cluster layer 31, only the individual case micro service cluster 311 corresponding to the newly added service scene needs to be deployed on the individual case logic micro service cluster layer 31, the general function corresponding to the newly added service scene is abstracted, and when the general function exists in the general logic micro service cluster layer 32, the calling relation between the individual case micro service cluster 311 and the corresponding general micro service cluster 321 of the newly added service scene is established; further, when the general-purpose function does not exist in the general-purpose logic micro service cluster layer 32, the general-purpose micro service cluster 321 corresponding to the general-purpose function may be deployed in the general-purpose logic micro service cluster layer 32, so as to implement horizontal expansion of the general-purpose logic micro service cluster layer 32 and vertical expansion of the service logic layer 3, so as to facilitate subsequent further service expansion and use. In conclusion, by means of the layered design of the service logic layer 3, horizontal and vertical new functions and new requirements can be further conveniently expanded, and the disorder of cross calling among a plurality of micro services can be effectively avoided.
Furthermore, in the data processing layer 4, a mode of setting micro service clusters is also adopted to support the horizontal scaling of a plurality of data processing micro service clusters 41, so as to support complex service data processing requirements.
In a preferred embodiment, the service logic layer 3 includes a micro service gateway interface 33, and the service logic layer 3 provides the service data to the application presentation layer 1 through the micro service gateway interface 33.
In the service logic layer 3, the micro service gateway interface 33, the case logic micro service cluster layer 31, and the general logic micro service cluster layer 32 are arranged in a hierarchy from top to bottom as a preferred embodiment.
Specifically, in this embodiment, the micro service gateway interface 33 is an API gateway interface, and the micro service gateway interface 33 is provided in the service logic layer 3, so that the case logic micro service cluster layer 31 and the general logic micro service cluster layer 32 that specifically perform service logic processing are effectively separated from the application presentation layer 1, so that the service logic layer 3 only exposes the micro service gateway interface 33 to the outside.
Further, the micro service gateway interface 33 provides service support for the application display layer 1 as the front end, so that each terminal application 2 of the application display layer 1 can obtain uniform service data to perform different display and submission operations, and extension and retraction of various service contacts which may appear in subsequent service scenes are facilitated. The service contact may be a plurality of applets or may be an H5 terminal.
As a preferred embodiment, the micro service gateway interface 33 implements data interaction with the application presentation layer 1 by using at least one gateway security check mode.
Specifically, in this embodiment, the gateway security check method includes, but is not limited to, an IP white list authentication and an AK/SK signature check method. The microservice gateway interface 33 preferably adopts multiple gateway security verification methods to ensure the security of data interaction with the application presentation layer 1, so that the microservice layered structure of the present application has certain security and robustness.
In a preferred embodiment, in the service logic layer 3, at least one general micro service cluster 321 is formed by abstracting general service logic from each predetermined service scene.
In the business logic layer 3, the case microservice cluster 311 inherits the common microservices provided by the corresponding common microservice cluster 321 in an object-oriented manner.
Specifically, in the present embodiment, in the service logic layer 3, the longitudinal service logic complexity is implemented in a service logic nesting manner, that is, first, a general service logic is abstracted from the service logic of a predetermined service scene as a general microservice, and then, a case microservice is expanded based on the general microservice. Taking a payment service scenario as an example, if a general payment micro-service can be used to solve most general payment scenarios, the general payment micro-service can be used as the general micro-service, and then individual case micro-services corresponding to individual case scenarios of different payment instances are expanded based on the general payment micro-service.
More specifically, the abstracted general micro service cluster 321 may have general operation steps and general attributes, the general micro service cluster 321 is used as a parent node of the micro service, an object-oriented idea is adopted to inherit the general micro service provided by using the parent node, and further, the step of refining a specific service scene and the specific attributes establish the relationship between an upper layer and a lower layer, so as to obtain the case micro service cluster 311 used as a child node, and the multiplexing relationship between the micro services is effectively optimized by multiplexing the abstracted general micro service.
In a preferred embodiment, each case micro service cluster 311 is deployed with a first load balancing module 312 and a plurality of case micro service nodes 313, and the first load balancing module 312 performs load balancing distribution according to the working state of each case micro service node 313.
Specifically, in this embodiment, by setting the first load balancing module 312 and the plurality of case micro service nodes 313, the service logic processing task performs load balancing distribution among the case micro service nodes 313, and simultaneously meets the requirement of a plurality of nodes on a simultaneous high-concurrency service scenario. Further, the expansion of the traffic can be realized by dynamically and elastically expanding the individual case micro service node 313. The first load balancing module 312 may implement load balancing distribution by using a reverse proxy load balancing manner.
In a preferred embodiment, each general microservice cluster 321 is deployed with a second load balancing module 322 and a plurality of general microservice nodes 323, and the second load balancing module 322 performs load balancing distribution according to the working state of each general microservice node 323.
Specifically, in this embodiment, by setting the second load balancing module 322 and the plurality of general microservice nodes 323, the service logic processing task performs load balancing distribution among the general microservice nodes 323, and simultaneously meets the requirement of a plurality of nodes on a high-concurrency service scenario. Further, the expansion of the traffic may be achieved by dynamic elastic expansion of the generic microservice node 323. The second load balancing module 322 may implement load balancing distribution by using a reverse proxy load balancing method.
In a preferred embodiment, a third load balancing module 411 and a plurality of data processing microservice nodes 412 are deployed in each data processing microservice cluster 41, and the third load balancing module 411 performs load balancing distribution according to the working state of each data processing microservice node 412.
Specifically, in this embodiment, by setting the third load balancing module 411 and the plurality of data processing micro service nodes 412, the service logic processing task performs load balancing distribution among the data processing micro service nodes 412, and simultaneously meets the requirement of a plurality of nodes on a high-concurrency service scenario. Further, the uncertain data concurrency requirements can be realized by dynamically and elastically expanding the data processing micro-service nodes 412, each data processing micro-service node 412 can be regarded as a single-core processor chip, a plurality of single-core processor chips can be opened simultaneously as multi-core processor chips according to requirements, and the uncertain data concurrency requirements are realized. The third load balancing module 411 may implement load balancing allocation in a reverse proxy load balancing manner.
In a preferred embodiment, each data processing microservice cluster 41 is further disposed with at least one database 413 and an access queue module 414 respectively connected to each data processing microservice node 412 and the database 413, and the access queue module 414 implements, in a queue manner, read/write operations of each data processing microservice node 412 on the database 413.
Specifically, in this embodiment, the access queue module 414 is configured to solve the database distributed transaction, and taking a write operation as an example, when a plurality of data processing microservice nodes 412 write data to a queue concurrently, the access queue module 414 uses a single thread to take charge of actually executing the operation database from the queue to solve the distributed transaction.
In a preferred embodiment, the case logic service cluster layer 31, the general logic micro service cluster layer 32 and the data processing layer 4 respectively implement flexible expansion of the case micro service cluster 311, the general micro service cluster 321 and the data processing micro service cluster 41 by using a containerization technique.
The application also provides a vehicle marketing system, which adopts the micro-service layered structure supporting flexible expansion.
As a preferred embodiment, taking a payment service as an example, the application presentation layer 1 and the service logic layer 3 in the micro service hierarchical structure are specifically described, as shown in fig. 2, the terminal application 2 in the application presentation layer 1 may include a WeChat to implement WeChat payment, the terminal application 2 may further include a Payment Bao to implement Payment Bao payment, the terminal application 2 may also be a Mobile terminal UnionPay application to implement Bank card Mobile payment, and the terminal application 2 may also be a payment application carried by a PC terminal to implement a corresponding payment service.
In the service logic layer 3, the various terminal applications 2 obtain the service data related to the payment service through the unified micro service gateway interface 33. The case logic micro service cluster layer 31 in the service logic layer 3 comprises three case micro service clusters 311, namely a charging micro service cluster 100 associated with a union pay service scene, a micro credit payment micro service cluster 200 associated with a micro credit payment service scene, and a payment micro service cluster 300 associated with a payment micro service scene, wherein the charging micro service cluster 100 comprises a charging service load balancer 101 and a charging micro service cluster 102 comprising a plurality of charging micro services, the micro credit payment micro service cluster 200 comprises a micro credit payment load balancer 201 and a micro credit payment micro service cluster 202 comprising a plurality of micro credit payment micro services, and the payment micro service cluster 300 comprises a payment micro service load balancer 301 and a payment micro service cluster 302 comprising a plurality of payment micro services.
Further, the generic logic microservice layer 32 in the business logic layer 3 includes three generic microservice clusters 321, including two generic microservice clusters 321 formed by abstracting generic logic from the business logic of the pay for business scenario of the union pay, the user management microservice cluster 400 and the subscription process microservice cluster 500, respectively, wherein the user management microservice cluster 400 includes a user management load balancer 401, and the user management microservice cluster 402 includes a plurality of user management microservices, and the subscription process microservice cluster 500 includes a subscription process load balancer 501, and a subscription process microservice cluster 502 including a plurality of subscription process microservices. Based on this, charging microservice cluster 100 implements Unionpay by invoking user management microservice cluster 400 and subscription flow microservice cluster 500 as general microservice cluster 321.
The general microservice cluster 321 further includes a general microservice cluster 321 formed by abstracting general logic from an associated microservice payment service scene and an associated paypal payment service scene, and the payment process microservice cluster 600 is a payment process microservice cluster 600, and the payment process microservice cluster 600 includes a payment process load balancer 601 and a payment process microservice cluster 602 including a plurality of payment process microservices. Based on this, the wechat payment microservice cluster 200 and the wechat payment microservice cluster 200 respectively realize wechat payment and pay payment by multiplexing the payment flow microservice cluster 600 as the general microservice cluster 321.
While the invention has been described with reference to a preferred embodiment, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention.
Claims (12)
1. A microservice hierarchy supporting flexible extensions, comprising:
the application display layer is used for providing service data for at least one terminal application so that the terminal application can display and operate the service data;
a service logic layer, wherein the service logic layer comprises a case logic micro service cluster layer and a general logic micro service cluster layer which are associated with a preset service scene, and the case logic micro service cluster in the case logic micro service cluster layer realizes the service logic processing of the associated preset service scene by calling the general micro service cluster in the general logic micro service cluster layer to obtain the corresponding service data;
the data processing layer comprises at least one data processing micro-service cluster and is used for providing storage read-write service for the service data obtained by the service logic layer;
the application display layer, the service logic layer and the data processing layer are arranged from top to bottom in a layered mode.
2. The micro-service hierarchy supporting flexible extensions according to claim 1, wherein the business logic layer comprises a micro-service gateway interface through which the business logic layer provides the business data to the application presentation layer.
3. The micro-service hierarchy supporting flexible extensions according to claim 2, wherein the business logic layer, the micro-service gateway interface, the case-specific micro-service cluster layer, and the generic micro-service cluster layer are hierarchically arranged from top to bottom.
4. The micro-service hierarchy supporting flexible extensions as claimed in claim 2, wherein the micro-service gateway interface implements data interaction with the application presentation layer using at least one gateway security check.
5. The micro-service hierarchy supporting flexible extensions according to claim 1, wherein in the service logic layer, common service logic is abstracted from each of the predetermined service scenes to form at least one of the common micro-service clusters.
6. The micro-service hierarchy supporting flexible expansion of claim 5, wherein in the business logic layer, the case micro-service cluster inherits, in an object-oriented manner, a common micro-service provided by using the corresponding common micro-service cluster.
7. The micro-service hierarchy structure supporting flexible expansion of claim 1, wherein each of the micro-service clusters is deployed with a first load balancing module and a plurality of micro-service nodes, and the first load balancing module performs load balancing distribution according to working states of the micro-service nodes.
8. The micro-service hierarchy structure supporting flexible expansion according to claim 1, wherein each of the general micro-service clusters is deployed with a second load balancing module and a plurality of general micro-service nodes, and the second load balancing module performs load balancing allocation according to a working state of each of the general micro-service nodes.
9. The micro-service hierarchy structure supporting flexible expansion of claim 1, wherein each of the data processing micro-service clusters is deployed with a third load balancing module and a plurality of data processing micro-service nodes, and the third load balancing module performs load balancing distribution according to the working status of each of the data processing micro-service nodes.
10. The micro-service hierarchy structure supporting flexible expansion of claim 9, wherein each of the data processing micro-service clusters is further deployed with at least one database and an access queue module respectively connected to each of the data processing micro-service nodes and the database, and the access queue module implements read-write operations of each of the data processing micro-service nodes on the database in a queue manner.
11. The micro-service hierarchy supporting flexible expansion of claim 1, wherein the case logic service cluster layer, the general logic micro-service cluster layer and the data processing layer respectively implement flexible expansion of the case logic micro-service cluster, the general micro-service cluster and the data processing micro-service cluster by using a containerization technology.
12. A vehicle marketing system, characterized in that a micro-service hierarchy supporting flexible extensions is employed as claimed in any one of claims 1-11.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011497278.6A CN112711396A (en) | 2020-12-17 | 2020-12-17 | Micro-service layered structure supporting flexible expansion |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011497278.6A CN112711396A (en) | 2020-12-17 | 2020-12-17 | Micro-service layered structure supporting flexible expansion |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112711396A true CN112711396A (en) | 2021-04-27 |
Family
ID=75544776
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011497278.6A Pending CN112711396A (en) | 2020-12-17 | 2020-12-17 | Micro-service layered structure supporting flexible expansion |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112711396A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113850536A (en) * | 2021-11-30 | 2021-12-28 | 阿里云计算有限公司 | Business customization method, display platform, server and storage medium |
| CN116136756A (en) * | 2023-04-18 | 2023-05-19 | 浪潮通用软件有限公司 | Layered structure-based microservice assembly method, device, equipment and medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6658432B1 (en) * | 2001-06-20 | 2003-12-02 | Microstrategy, Inc. | Method and system for providing business intelligence web content with reduced client-side processing |
| CN105162884A (en) * | 2015-09-25 | 2015-12-16 | 浪潮(北京)电子信息产业有限公司 | Cloud management platform based on micro-service architecture |
| CN107463365A (en) * | 2016-08-24 | 2017-12-12 | 上海幸福九号网络科技有限公司 | A kind of SOA solution systems and method |
| CN107786379A (en) * | 2017-11-15 | 2018-03-09 | 四川省龙逸凤集网络科技有限公司 | A kind of layering cloud management platform based on micro services framework |
| CN108933807A (en) * | 2017-05-27 | 2018-12-04 | 广州市呼百应网络技术股份有限公司 | A kind of layer-stepping project service platform |
| CN110149396A (en) * | 2019-05-20 | 2019-08-20 | 华南理工大学 | A kind of platform of internet of things construction method based on micro services framework |
| CN111274027A (en) * | 2020-01-09 | 2020-06-12 | 山东汇贸电子口岸有限公司 | Multi-live load balancing method and system applied to openstack cloud platform |
-
2020
- 2020-12-17 CN CN202011497278.6A patent/CN112711396A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6658432B1 (en) * | 2001-06-20 | 2003-12-02 | Microstrategy, Inc. | Method and system for providing business intelligence web content with reduced client-side processing |
| CN105162884A (en) * | 2015-09-25 | 2015-12-16 | 浪潮(北京)电子信息产业有限公司 | Cloud management platform based on micro-service architecture |
| CN107463365A (en) * | 2016-08-24 | 2017-12-12 | 上海幸福九号网络科技有限公司 | A kind of SOA solution systems and method |
| CN108933807A (en) * | 2017-05-27 | 2018-12-04 | 广州市呼百应网络技术股份有限公司 | A kind of layer-stepping project service platform |
| CN107786379A (en) * | 2017-11-15 | 2018-03-09 | 四川省龙逸凤集网络科技有限公司 | A kind of layering cloud management platform based on micro services framework |
| CN110149396A (en) * | 2019-05-20 | 2019-08-20 | 华南理工大学 | A kind of platform of internet of things construction method based on micro services framework |
| CN111274027A (en) * | 2020-01-09 | 2020-06-12 | 山东汇贸电子口岸有限公司 | Multi-live load balancing method and system applied to openstack cloud platform |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113850536A (en) * | 2021-11-30 | 2021-12-28 | 阿里云计算有限公司 | Business customization method, display platform, server and storage medium |
| CN116136756A (en) * | 2023-04-18 | 2023-05-19 | 浪潮通用软件有限公司 | Layered structure-based microservice assembly method, device, equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107566153B (en) | Self-management micro-service implementation method | |
| CN110795486A (en) | Micro-service platform | |
| CN110262902B (en) | Information processing method and system, medium, and computing device | |
| CN112711396A (en) | Micro-service layered structure supporting flexible expansion | |
| CN101373428A (en) | System for integrating intermediate parts | |
| CN109358956A (en) | Service calling method | |
| CN107291456A (en) | The control method and system of a kind of multihead display | |
| CN109104491A (en) | A kind of micro services call method, device, server and storage medium | |
| KR20080064587A (en) | Open framework system for heterogeneous computing and service integration | |
| CN112000463A (en) | GPU resource allocation method, system, terminal and storage medium based on CUDA | |
| CN110300165A (en) | A kind of call method of function program, device, equipment and storage medium | |
| CN112398936A (en) | Kubernetes-based multi-network card container implementation method and system | |
| CN114710571A (en) | Data packet processing system | |
| CN106789421A (en) | The method and apparatus of collaborative design | |
| CN110737425A (en) | billing platform system application program establishing method and device | |
| CN113377493A (en) | Container cloud simulation system and design method thereof | |
| US10135752B2 (en) | Expansion device for virtual interface and network server system thereof | |
| US8533747B2 (en) | Method and system for selecting one or more integrated circuit card interface devices | |
| US20050125486A1 (en) | Decentralized operating system | |
| Berry et al. | The A1√ architecture model | |
| CN113051335A (en) | Transformation method for private cloud multi-tenant shared application system | |
| CN106598551B (en) | A kind for the treatment of method and apparatus of smart card, smart card | |
| CN110648081A (en) | Business modeling method and device for computing system and computer system | |
| CN109086067A (en) | A kind of BIOS standby update method, apparatus, terminal and storage medium | |
| CN109254863A (en) | A kind of method, apparatus and controlled terminal recording System Event Log |
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 |