CN112487333A - Data center design method and system based on micro-service - Google Patents
Data center design method and system based on micro-service Download PDFInfo
- Publication number
- CN112487333A CN112487333A CN202011369132.3A CN202011369132A CN112487333A CN 112487333 A CN112487333 A CN 112487333A CN 202011369132 A CN202011369132 A CN 202011369132A CN 112487333 A CN112487333 A CN 112487333A
- Authority
- CN
- China
- Prior art keywords
- service
- data
- module
- current
- party
- 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
- 238000000034 method Methods 0.000 title claims abstract description 23
- 238000012544 monitoring process Methods 0.000 claims description 12
- 230000004044 response Effects 0.000 claims description 4
- 239000000126 substance Substances 0.000 claims description 2
- 238000007726 management method Methods 0.000 description 12
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000004913 activation Effects 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 230000009849 deactivation Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
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
- G06F16/972—Access to data in other repository systems, e.g. legacy data or dynamic Web page generation
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention provides a design method of a data center based on micro-service, which comprises the steps of obtaining the current implementation party of the data service to be registered; wherein, the current implementation party is a data center or a third party service producer; and determining the data service to be registered corresponding to the current implementer, selecting a service user registration module, a service registration module and corresponding modules except the service user registration module and the service registration module from a preset module library, combining to obtain the data service registered by the current implementer, and further adding the data service to the data center. The invention can solve the problems that the newly added data service in the existing data can not be realized and the data service provided by a third-party service producer can not be accessed.
Description
Technical Field
The invention relates to the technical field of data service, in particular to a design method and a system of a data center station based on micro service.
Background
At present, most data middleboxes adopt a design mode of centralized data management, and all general data services are realized by the data middleboxes. However, once a data center station needs to add a new data service of a special service, it is difficult to implement efficiently, and it is also impossible to freely and timely access the data service provided by a third party service producer.
Disclosure of Invention
The technical problem to be solved by the embodiments of the present invention is to provide a method and a system for designing a data center based on a micro-service, which can overcome the problems that a new data service cannot be implemented in the existing data center and a data service provided by a third-party service producer cannot be accessed.
In order to solve the above technical problem, an embodiment of the present invention provides a method for designing a data center based on microservice, where the method includes the following steps:
s1, acquiring the current implementation party of the data service to be registered; wherein the current implementer is a data middlebox or a third party service producer;
s2, determining the data service to be registered corresponding to the current implementer, selecting the service user registration module, the service registration module and the corresponding modules except the service user registration module and the service registration module from a preset module library, combining to obtain the data service registered by the current implementer, and further adding the data service to the data center.
The preset module library comprises a service user registration module, a service application module, a service calling module, a service inquiry module, a service user management module, a service monitoring module and a workflow module.
Wherein, the step S2 specifically includes:
when the data service to be registered corresponding to the current implementer is at least one of application, calling, inquiry, monitoring and user management, selecting the service user registration module and the service registration module, selecting the workflow module, and further selecting one or more corresponding service application module, the service calling module, the service inquiry module, the service monitoring module and the service user management module from the preset module library, combining to obtain the data service registered by the current implementer and further adding the data service to the data center platform.
If the current implementation party is a third-party service producer, the objects served by the service user registration module and the service user management module both comprise a service consumer and the third-party service producer.
If the current implementation party is a data center station, the objects served by the service user registration module and the service user management module are only service consumers.
The service user registration module is provided with a unified standard information field, which comprises an external system name, an external system English name for short, an external system IP, an external system port, a service password update Rest service address, a service password update safety code, an applicant, an application reason, an applicant mobile phone number and a mailbox.
The service registration module is provided with a uniform standard information field, and comprises a service name, a service type, a service protocol, a service URL, a service security level, an applicant mobile phone number, a mailbox, a service scene description, a service data source, a reference, a return value, a request message example, a response message example, an external system name, an external system English name and an external system English name short for name.
The service types comprise interface service, file service and page service; the Service protocols comprise a Rest protocol, a Web Service protocol, an Txt protocol, a Zip protocol and a page protocol; wherein the content of the first and second substances,
the interface Service comprises a Rest protocol and a Web Service protocol;
the file service comprises Txt protocol and Zip protocol;
the page service includes a page protocol.
The service monitoring module is provided with a uniform standard information field, which comprises a data service user ID, an external system server IP, an external system server port, a data service ID, a data service name, a data service password, a service calling state, a service calling start time, a service calling end time and a service calling log.
The embodiment of the invention also provides a data center design system based on the micro service, which comprises the following steps:
the data service registration method comprises an implementation party acquisition unit, a registration unit and a registration unit, wherein the implementation party acquisition unit is used for acquiring a current implementation party of a data service to be registered; wherein the current implementer is a data middlebox or a third party service producer;
and the data service registration unit is used for determining the data service to be registered corresponding to the current implementer, selecting the service user registration module, the service registration module and corresponding modules except the service user registration module and the service registration module from a preset module library, combining to obtain the data service registered by the current implementer, and further adding the data service to the data center.
The embodiment of the invention has the following beneficial effects:
the invention identifies the data center station of the data service to be registered or a third party service producer, and combines the service user registration module, the service registration module and other modules except the service user registration module and the service registration module which are designed in a modularized way to obtain the corresponding data service, thereby realizing that the data service registered by the data center station or the third party service producer can be quickly added to the data center station, and overcoming the problems that the newly added data service of the existing data center station can not be realized and the data service provided by the third party service producer can not be accessed.
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 introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is within the scope of the present invention for those skilled in the art to obtain other drawings based on the drawings without inventive exercise.
Fig. 1 is a flowchart of a method for designing a data center based on microservice according to an embodiment of the present invention;
fig. 2 is a connection block diagram of each function module included in a preset module library in the method for designing a data center based on a microservice according to the embodiment of the present invention;
fig. 3 is a schematic structural diagram of a data center design system based on microservice according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in further detail with reference to the accompanying drawings.
As shown in fig. 1, in an embodiment of the present invention, a method for designing a data center based on microservice proposed by the inventor includes the following steps:
step S1, acquiring the current implementation party of the data service to be registered; wherein the current implementer is a data middlebox or a third party service producer;
step S2, determining the data service to be registered corresponding to the current implementer, and selecting the service user registration module, the service registration module, and the corresponding modules except the service user registration module and the service registration module from a preset module library, combining them to obtain the data service registered by the current implementer, and further adding the data service to the data center.
In step S1, it is necessary to consider whether the data service provided by the middle station automatically registers in the data center station is added quickly or the data service of a third party other than the middle station is accessed freely and timely. Therefore, it is determined that the current implementation of the data service to be registered is a data middlebox or third party service producer.
In step S2, first, the data service is modularly managed based on the micro service form.
A module library composed of a plurality of modularly designed functional modules is predefined, and the module library comprises but is not limited to a service user registration module, a service application module, a service calling module, a service inquiry module, a service user management module, a service monitoring module and a workflow module.
As shown in fig. 2, each of the functional modules adopts a standardized module design and is defined accordingly, which is specifically as follows:
(1) the service user registration module is provided with a unified standard information field which comprises an external system name, an external system English name for short, an external system IP, an external system port, a service password updating Rest service address (used for service password synchronization), a service password updating security code (used for service password synchronization), an applicant, an application reason, an applicant mobile phone number and a mailbox. It should be noted that the application approval is performed through the workflow module, and after the application approval passes, the service user account can be generated to perform related operations such as registration, query, application, invocation, and the like.
When the current implementation party is a third-party service producer, the objects served by the service user registration module comprise a service consumer and the third-party service producer; when the current implementation party is a data middlebox, the object served by the service user registration module is only a service consumer.
(2) The service registration module is provided with a uniform standard information field, which comprises a service name, a service type, a service protocol, a service URL (http address or SFTP IP), a service security level (1 level, 2 levels and 3 levels), a mobile phone number of an applicant, a mailbox, a service scene description, a service data source, an access parameter (service call), a return value (service call), a request message example (service call message example), a response message example (service call message example), an external system name, an external system English name and an external system English name short for name. It should be noted that the service producer who owns the service user account can register the middlebox service and the third party service.
The service types comprise interface service, file service and page service; the Service protocols include the Rest protocol, the Web Service protocol, the Txt protocol, the Zip protocol, and the page protocol. The interface Service comprises a Rest protocol and a Web Service protocol; file services include the Txt protocol and the Zip protocol; the page service includes a page protocol. It is understood that the Rest protocol means that the data provision manner is a Rest interface; the Web Service protocol represents that the data providing mode is a Web Service interface; txt the protocol indicates that the data is provided as a text file; the Zip protocol represents that the data providing mode is a compressed file; the page protocol indicates that the data is provided as a page.
When the current implementation party is a third-party service producer, the object served by the service registration module is the third-party service producer; when the current implementation party is the data center station, the object served by the service registration module is only the data center station itself.
(3) The service application module applies and approves through the workflow module, after the application and approval are passed, the system automatically generates service passwords corresponding to the service application one by one, and the service passwords can be automatically or manually synchronized to service consumers. The service password is valid for a default period of 30 days, and after the expiration period, the service password can be automatically or manually refreshed so as to continue to access the data service for a longer period.
It should be noted that all data services can be managed on the service inquiry page, the activation and deactivation operations can be performed manually, and the service application operation can be performed only when the service is in an activated state. Meanwhile, the object served by the service application module is a service consumer with a service user account, and for all enabled data services, the data service required by the service can be inquired and selected, and the service application can be submitted.
(4) The service calling module can immediately call the successfully applied data service according to the service scene description of the data service, and simultaneously needs to provide a corresponding service password. In the calling process, the data center station can automatically check whether the called data service is matched with the service password, and can carry out substantial service calling after the verification is passed, and returns a response result. The service call details are recorded in a log table.
It should be noted that the object served by the service invocation module is a service consumer who owns the account of the service user.
(5) The service inquiry module inquires the registered service, so that the required service is convenient to select.
(6) The service user management module manages accounts, authorities and the like for service producers and service consumers of the data service. If the current implementation party is a third-party service producer, the objects served by the service user management module comprise a service consumer and the third-party service producer; if the current implementation party is a data middlebox, the object served by the service user management module is only a service consumer.
(7) The service monitoring module monitors the called service, and the information about the success and failure of service calling is recorded. The service monitoring module has uniform standard information fields, including data service user ID, external system server IP, external system server port, data service ID, data service name, data service password, service calling state (1 success, 0 failure), service calling start time, service calling end time and service calling log.
(8) The workflow module provides workflow support for the service user registration module, the service user management module and the service application module.
Compared with the prior loose, messy and endless data API access mode, the data service users are classified and managed by adopting a producer and consumer mode, the data service users are more centralized and convenient, the subsequent data service is updated, and the relevant service users can be automatically and timely notified according to the relevant information registered by the service users.
And secondly, providing data services of different service types according to different service use scenes, and effectively improving the use efficiency of key service data. Therefore, according to the data service to be registered corresponding to the current implementation party, the function module combination can be performed in the module library to obtain the corresponding data service, specifically:
when the data service to be registered corresponding to the current implementer is at least one of application, call, query, monitoring and user management, selecting a service user registration module and a service registration module, selecting a workflow module, and further selecting one or more corresponding service application module, a service call module, a service query module, a service monitoring module and the service user management module from the preset module library, combining to obtain the data service registered by the current implementer and further adding the data service to the data center.
It should be noted that data services should be specifically directed to application services, such as applications, queries, etc. Therefore, a service object requiring a data service, namely, a service user, has a registered consumer (i.e., a service provider) under a registration module, at which time the workflow module may be required to perform an approval (or may not be required to perform the approval), and a provider of the data service, namely, a registration party under the registration module of the service (such as a data middlebox itself or a third-party producer) is required.
As shown in fig. 3, a system for designing a data center based on a microservice according to an embodiment of the present invention includes:
an implementer acquiring unit 110, configured to acquire a current implementer of the data service to be registered; wherein the current implementer is a data middlebox or a third party service producer;
the data service registration unit 120 is configured to determine that the current implementer corresponds to a data service to be registered, select, in a preset module library, the service user registration module and the service registration module, and select a corresponding module except the service user registration module and the service registration module, combine the two modules to obtain the data service registered by the current implementer, and add the data service to the data center.
The embodiment of the invention has the following beneficial effects:
the invention identifies the data center station of the data service to be registered or a third party service producer, and combines the service user registration module, the service registration module and other modules except the service user registration module and the service registration module which are designed in a modularized way to obtain the corresponding data service, thereby realizing that the data service registered by the data center station or the third party service producer can be quickly added to the data center station, and overcoming the problems that the newly added data service of the existing data center station can not be realized and the data service provided by the third party service producer can not be accessed.
It should be noted that, in the above system embodiment, each included unit is only divided according to functional logic, but is not limited to the above division as long as the corresponding function can be implemented; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention.
It will be understood by those skilled in the art that all or part of the steps in the method for implementing the above embodiments may be implemented by relevant hardware instructed by a program, and the program may be stored in a computer-readable storage medium, such as ROM/RAM, magnetic disk, optical disk, etc.
The above disclosure is only for the purpose of illustrating the preferred embodiments of the present invention, and it is therefore to be understood that the invention is not limited by the scope of the appended claims.
Claims (10)
1. A design method of a data center based on micro service is characterized by comprising the following steps:
s1, acquiring the current implementation party of the data service to be registered; wherein the current implementer is a data middlebox or a third party service producer;
s2, determining the data service to be registered corresponding to the current implementer, selecting the service user registration module, the service registration module and the corresponding modules except the service user registration module and the service registration module from a preset module library, combining to obtain the data service registered by the current implementer, and further adding the data service to the data center.
2. The method of claim 1, wherein the predetermined library of modules includes a service user registration module, a service application module, a service invocation module, a service query module, a service user management module, a service monitoring module, and a workflow module.
3. The method for designing a data center based on microservice of claim 2, wherein the step S2 specifically comprises:
when the data service to be registered corresponding to the current implementer is at least one of application, calling, inquiry, monitoring and user management, selecting the service user registration module and the service registration module, selecting the workflow module, and further selecting one or more corresponding service application module, the service calling module, the service inquiry module, the service monitoring module and the service user management module from the preset module library, combining to obtain the data service registered by the current implementer and further adding the data service to the data center platform.
4. The method of claim 3, wherein if the current implementation party is a third party service producer, the objects served by the service consumer registration module and the service consumer management module comprise a service consumer and a third party service producer.
5. The method of claim 3, wherein if the current implementation is a data center, the objects served by the service subscriber registration module and the service subscriber management module are only service consumers.
6. The method as claimed in claim 4 or 5, wherein the service user registration module has a uniform standard information field, which includes an external system name, an external system english name abbreviation, an external system IP, an external system port, a service password update Rest service address, a service password update security code, the applicant, an application reason, an applicant phone number, and a mailbox.
7. The method according to claim 4 or 5, wherein the service registration module has uniform standard information fields including service name, service type, service protocol, service URL, service security level, applicant's mobile phone number, mailbox, service scenario description, service data source, entry, return value, request message instance, response message instance, external system name, external system English name, and external system English name abbreviation.
8. The method of claim 7, wherein the service types include interface services, file services, and page services; the Service protocols comprise a Rest protocol, a Web Service protocol, an Txt protocol, a Zip protocol and a page protocol; wherein the content of the first and second substances,
the interface Service comprises a Rest protocol and a Web Service protocol;
the file service comprises Txt protocol and Zip protocol;
the page service includes a page protocol.
9. The method of claim 4 or 5, wherein the service monitor module has a uniform standard information field comprising a data service user ID, an external system server IP, an external system server port, a data service ID, a data service name, a data service password, a service call status, a service call start time, a service call end time, and a service call log.
10. A data center design system based on microservice, comprising:
the data service registration method comprises an implementation party acquisition unit, a registration unit and a registration unit, wherein the implementation party acquisition unit is used for acquiring a current implementation party of a data service to be registered; wherein the current implementer is a data middlebox or a third party service producer;
and the data service registration unit is used for determining the data service to be registered corresponding to the current implementer, selecting the service user registration module, the service registration module and corresponding modules except the service user registration module and the service registration module from a preset module library, combining to obtain the data service registered by the current implementer, and further adding the data service to the data center.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011369132.3A CN112487333A (en) | 2020-11-30 | 2020-11-30 | Data center design method and system based on micro-service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011369132.3A CN112487333A (en) | 2020-11-30 | 2020-11-30 | Data center design method and system based on micro-service |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112487333A true CN112487333A (en) | 2021-03-12 |
Family
ID=74936980
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011369132.3A Pending CN112487333A (en) | 2020-11-30 | 2020-11-30 | Data center design method and system based on micro-service |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112487333A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110798490A (en) * | 2020-01-06 | 2020-02-14 | 广州欧赛斯信息科技有限公司 | Method and device for accessing third-party system based on data center and data center |
| CN111008197A (en) * | 2019-11-20 | 2020-04-14 | 王锦志 | Data center design method for power marketing service system |
| CN111181943A (en) * | 2019-12-24 | 2020-05-19 | 平安医疗健康管理股份有限公司 | Service interaction method and device based on service middlebox, computer equipment and computer storage medium |
| CN111667305A (en) * | 2020-05-24 | 2020-09-15 | 杭州云徙科技有限公司 | Digital middle station system, construction method and application method |
| CN111858731A (en) * | 2020-07-13 | 2020-10-30 | 南通数博信息科技有限公司 | Data relay station system for data integration processing and service sharing based on big data virtualization technology |
-
2020
- 2020-11-30 CN CN202011369132.3A patent/CN112487333A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111008197A (en) * | 2019-11-20 | 2020-04-14 | 王锦志 | Data center design method for power marketing service system |
| CN111181943A (en) * | 2019-12-24 | 2020-05-19 | 平安医疗健康管理股份有限公司 | Service interaction method and device based on service middlebox, computer equipment and computer storage medium |
| CN110798490A (en) * | 2020-01-06 | 2020-02-14 | 广州欧赛斯信息科技有限公司 | Method and device for accessing third-party system based on data center and data center |
| CN111667305A (en) * | 2020-05-24 | 2020-09-15 | 杭州云徙科技有限公司 | Digital middle station system, construction method and application method |
| CN111858731A (en) * | 2020-07-13 | 2020-10-30 | 南通数博信息科技有限公司 | Data relay station system for data integration processing and service sharing based on big data virtualization technology |
Non-Patent Citations (1)
| Title |
|---|
| 程旺编著: "企业数据治理与SAP MDG实现", 30 September 2020, 北京：机械工业出版社, pages: 259 - 260 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7676473B2 (en) | Propagation of user preferences to end devices | |
| US8612568B2 (en) | Method, system and network server for recording use of network service capability by applications | |
| US20080244610A1 (en) | Method and Apparatus for Dynamic Device Allocation for Managing Escalation of On-Demand Business Processes | |
| US8126962B1 (en) | Systems and methods for tracking user activity at website | |
| CN112612629A (en) | Method and system for realizing component type data interface | |
| CA3062580A1 (en) | An enterprise group establishing method and computer device in an instant message system | |
| CN108989189B (en) | Message pushing method based on enterprise WeChat | |
| CN103188131A (en) | Method and device for friend recommending on instant messaging client side | |
| CN107959615B (en) | Data transmission method, user equipment and service equipment | |
| CN110109766B (en) | Data interaction method and device based on cross-department and cross-platform data sharing exchange | |
| US7596504B2 (en) | Management of support center calls | |
| CN104754009A (en) | Service acquisition and invocation method, device, client-side and server | |
| CN110750780B (en) | User role permission fusion method, device and equipment based on multi-service system | |
| EP2442487A1 (en) | Location processing method address duplication processing method and device | |
| US20060069783A1 (en) | Program, method and device for managing information shared among components, recording medium and communication apparatus | |
| US8037067B1 (en) | Systems and methods for tracking user activity at website | |
| CN101957830A (en) | System, device and method for inquiring lists | |
| US20090077243A1 (en) | Conversation recovery method | |
| CN112487333A (en) | Data center design method and system based on micro-service | |
| JP2010516218A (en) | Improved telecommunications greeting system | |
| CN110087232A (en) | A kind of call processing method based on smart machine, device and server | |
| CN104346228A (en) | Application program sharing method and terminal | |
| CN111506644B (en) | Application data processing method and device and electronic equipment | |
| CN111240750B (en) | Awakening method and device for target application program | |
| US20080033961A1 (en) | Electronic Document Browsing |
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 |