CN114579493A - Mechanism for reducing software coupling degree through software type data interaction bus - Google Patents
Mechanism for reducing software coupling degree through software type data interaction bus Download PDFInfo
- Publication number
- CN114579493A CN114579493A CN202210201993.3A CN202210201993A CN114579493A CN 114579493 A CN114579493 A CN 114579493A CN 202210201993 A CN202210201993 A CN 202210201993A CN 114579493 A CN114579493 A CN 114579493A
- Authority
- CN
- China
- Prior art keywords
- data
- module
- software
- input end
- subscriber
- 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
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/382—Information transfer, e.g. on bus using universal interface adapter
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/42—Bus transfer protocol, e.g. handshake; Synchronisation
- G06F13/4204—Bus transfer protocol, e.g. handshake; Synchronisation on a parallel bus
- G06F13/4208—Bus transfer protocol, e.g. handshake; Synchronisation on a parallel bus being a system bus, e.g. VME bus, Futurebus, Multibus
-
- 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/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Multi Processors (AREA)
Abstract
The invention discloses a mechanism for reducing software coupling degree through a software type data interaction bus, and a universal development framework of data interaction realized based on publishing and subscribing, aiming at isolating a publisher and a subscriber through bus type management so as to realize reduction of software coupling degree, wherein the output end of the subscriber is connected with the input end of a connection module, and a service management module is connected with the publisher in a two-way manner; the subscriber only concerns the needed data, but not how to generate the data, the publisher and the subscriber perform uplink data and downlink data interaction through an asynchronous interface of a bus, the data is in a standardized data format and is packaged into standard data interfaces such as attributes, methods and notifications, the bus is responsible for synchronization and notification of the data, standardized messages are transmitted on the bus, a plurality of data formats are supported, and a universal development framework is formed through the mechanism.
Description
Technical Field
The invention relates to the technical field of software coupling degree, in particular to a mechanism for reducing the software coupling degree through a software type data interaction bus.
Background
Coupling (or Coupling) is a software measure, which refers to the degree of information or parameter dependency between modules in a program. Cohesion is a concept as opposed to coupling, in general low coupling represents high cohesion and vice versa. Both coupling and cohesion are proposed by Lihresconstatin, which proposes a structural design concept [1 ]. Low coupling is a characteristic of well-structured programs, and readability and maintainability of low coupling programs can be better.
Currently, there are four general ways to reduce the software coupling degree: the software coupling degree is reduced through programming skills, the software coupling degree is reduced through a design mode, the software coupling degree is reduced through reduction of logic dependence, and the software coupling degree is reduced through a software framework.
The software coupling degree reduced by the programming skill is generally limited by the programming platform, language and programming level, the technical threshold is higher, the skill cannot be reused among different projects, higher programming experience is needed as a basis, and the software coupling degree tends to be optimized in a customized manner.
The software coupling degree is reduced through a design mode, the design of a common mode is single, and the coupling degree exists among a plurality of design modes; the granularity of the single mode for reducing the coupling degree is relatively coarse, the logic dependence in a module cannot be solved, and the coupling degree with fine granularity still exists.
The software coupling degree is reduced by reducing the logic dependence, the software coupling degree is mostly caused by direct dependence or indirect dependence among logics, the dependence on a syntax level can be solved or reduced by programming skills, but the dependence among the logics cannot be avoided, the call among the logics occurs at any time, and if the software dependence is reduced by reducing the logic requirement, the coupling degree is reduced by sacrificing the software function.
The software coupling degree reduced by the software framework is relatively dependent on the existing software framework, the software framework is similar to a design mode, the coupling degree is reduced by top-level design, the coupling degree of the software top-level can be reduced to a certain degree, the software implementation range is limited by the framework, the software implementation range is realized according to the framework specification, the software implementation flexibility cannot be guaranteed, the expansibility is poor, and meanwhile, the logic coupling degree in the module cannot be solved by the design similar to the mode.
Disclosure of Invention
The present invention is directed to a mechanism for reducing software coupling degree through a software-based data interaction bus, so as to solve the problems in the background art.
Definition of the bus: the universal data bus provides a data interaction channel and publishes and subscribes services;
definition of the publisher: the data provider is responsible for collecting data from the bottom layer and carrying out logic operation, for example, collecting original data from a network or a CAN bus; the data are issued upwards, and original data are packaged into data to be finally expressed according to a data protocol and issued to a bus;
definition of the subscriber: the data user is connected with the bus downwards, subscribes the required data and is responsible for displaying the data in different forms upwards. Such as labels, lists, progress bars, charts, animations, etc.
In order to achieve the purpose, the invention provides the following technical scheme:
a mechanism for reducing software coupling degree through a software type data interaction bus comprises the data interaction bus, standardized messages, a subscriber, a publisher, a connection module, a service management module and a universal development framework formed based on the mechanism, wherein the universal development framework comprises the publisher, the service manager, the data interaction bus, the connection module and the subscriber, the output end of the publisher is connected with the input end of the data interaction bus, the publisher and the service manager are connected in a two-way mode, the subscriber and the connection module are connected in a two-way mode, and the output end of the connection module is connected with the input end of the data interaction bus.
As a still further scheme of the invention: the output end of the standardized message is a data bus in a process or between processes or between networks, the data interaction bus is respectively in two-way connection with the connection module and the service management module, the connection module is in two-way connection with the subscriber, the subscriber is in two-way connection with the data display module, and the service management module is in two-way connection with the publisher.
As a still further scheme of the invention: the mechanism can be used for in-process scopes, and can be extended to inter-process scopes, and can also be extended to inter-network scopes.
As a still further scheme of the invention: the input end of the interprocess scope is respectively connected with the output ends of the first connecting module and the first service management module, the output end of the first connecting module is connected with the input end of the first subscriber module, and the output end of the first service management module is connected with the input end of the first publisher module.
As a still further scheme of the invention: the input end of the scope in the process is respectively connected with the output ends of the second connecting module and the third service management module, the output end of the second connecting module is connected with the input end of the second subscriber module, and the output end of the third service management module is connected with the input end of the third publisher module.
As a still further scheme of the invention: the input end of the inter-network scope is respectively connected with the output ends of the third connecting module and the second service management module, the output end of the third connecting module is connected with the input end of the third subscriber module, and the output end of the second service management module is connected with the input end of the second publisher module.
As a still further scheme of the invention: the data interaction bus and the data synchronization interface call to realize bidirectional connection, the data synchronization interface call respectively realizes bidirectional connection with the subscriber and the publisher, the data interaction bus and the interface realize bidirectional connection, the interface respectively realizes bidirectional connection with the data subscription/request and the data publishing/notification, the data subscription/request and the data display module realize bidirectional connection, and the data publishing/notification respectively realizes bidirectional connection with the service logic and the life cycle management.
As a still further scheme of the invention: the uplink data comprises that the output end of the data display module is connected with the input end of the subscriber, the output end of the subscriber is connected with the input end of the connection module, the output end of the original data module is connected with the input end of the publisher, the output end of the publisher is connected with the input end of the standard data module, the output end of the standard data module is connected with the input end of the standard data interface, and the output ends of the standard data interface and the connection module are both connected with the input end of the data interaction bus.
As a still further scheme of the invention: the downlink data comprises that the output end of the subscriber is connected with the input end of the connecting module, and the output end of the connecting module is connected with the output end of the data interaction bus and the input end of the publisher.
As a still further scheme of the invention: the input end of the universal development frame is connected with the output end of the sub-interface module, and the output end of the universal development frame is respectively connected with the input ends of the dynamic micro-service and the resident micro-service.
Compared with the prior art, the invention has the beneficial effects that:
1. the invention defines the data publisher and the data subscriber separately by the isolation of the bus, and the publisher only concerns the collection and the publishing of the data, but not the use of the data by the user; the subscriber only concerns the data needed, which data source will provide the data, but not how the data is generated, when the bus data is updated, the standardized data will be automatically synchronized to the subscriber, and the subscriber's request will be transmitted through the bus, completely decoupled logically, and the scope of this decoupling can be extended between multiple areas, ranging from intra-process, inter-process, to local area networks, and even wide area networks.
2. The invention has the advantages that the invention uses the bus mechanism to reduce the cooperation among engineers, the business logic developer in charge of the data publisher does not need to relate to how the data user displays the data, the engineer in charge of the data display does not need to relate to how the data of the publisher is generated, the engineer in charge of the data display only needs to maintain one data interaction protocol, the data interaction protocol is negotiated and customized in the design stage, the data is published and subscribed according to the protocol, the bus isolates the publisher and subscriber, the developer in charge of the data publication and the developer in charge of the data subscription are virtually isolated, the coupling degree of cooperation is reduced, and the developer can be out of one area or even cooperate among networks through the expansion of the scope of action.
3. The bus mechanism of the invention reduces the cooperative coupling degree, provides great convenience for development and debugging, and a data publishing engineer can check whether the data logic is correct or not through self-testing according to the cooperative data interaction protocol without waiting for the completion of data display; the data user does not need to wait for the completion of the real data release, and can complete self-test according to the data interaction protocol, so that both the data user and the data user can complete self-test and self-regulation by means of the bus. The joint debugging stage can depend on the communication back end provided by the bus, and the debugging can be extended to the combined debugging of multiple modes such as single-process debugging, multi-process debugging, remote debugging, cloud debugging and the like without depending on external input and feedback.
4. The invention has no strong dependence between the publisher and the subscriber, the modules only generate association through the bus, and the association is generated by the standard data interface and the data protocol, so the publisher can not sense the existence of the subscriber, only provides the data publishing service, and any subscriber can subscribe the required data only by associating the service through the bus, thereby increasing the reusability of the publisher. Similarly, the subscriber cannot sense the existence of the publisher, only the data service is associated through the bus, and if the data service exists, the subscriber can subscribe the required data, so that the reusability of the subscriber is increased.
5. The invention can realize a universal development frame by using the bus mechanism on the basis of improving the reusability of software publishers and subscribers, the core is to define the universal interfaces and data encapsulation of the publishers, the subscribers and the service managers on the bus, and the peripheral variable logic can be in seamless butt joint through the frame to complete a universal platform frame.
Drawings
FIG. 1 is a schematic diagram of a system architecture of a mechanism for reducing software coupling via a software-based data interaction bus;
FIG. 2 is a block diagram of a data interaction bus in a mechanism for reducing software coupling via a software-based data interaction bus;
FIG. 3 is a diagram of a bus-based role relationship between publish-subscribe requests in a mechanism for reducing software coupling via a software-based data interaction bus;
FIG. 4 is a schematic diagram of an actual deployment scenario of a mechanism for reducing software coupling via a software-based data interaction bus;
FIG. 5 is a schematic diagram of a system architecture for uplink data in a mechanism for reducing software coupling via a software-based data interaction bus;
FIG. 6 is a schematic diagram of a structure of downlink data in a mechanism for reducing software coupling via a software-based data interaction bus;
FIG. 7 is a general development framework diagram of a development framework implemented based on a software interaction bus mechanism in a mechanism for reducing software coupling degree through the software interaction bus;
fig. 8 is a schematic structural diagram of a generic development framework in a mechanism for reducing software coupling degree through a software-based data interaction bus.
In the figure: 1. standardizing the message; 2. an interprocess scope; 3. an in-process scope; 4. an inter-network scope; 5. a data interaction bus; 6. a connection module; 61. a first connecting module; 62. a second connecting module; 63. a third connecting module; 7. a subscriber; 71. a first subscriber module; 72. a subscriber module II; 73. a third subscriber module; 8. a data display module; 9. a service management module; 10. a publisher; 101. a first publisher module; 102. a second publisher module; 103. a third publisher module; 11. calling a data synchronization interface; 12. interfaces (attributes, methods, notifications); 13. data subscription/request; 14. data publishing/notification; 15. managing a life cycle; 16. business logic; 17. a commonality development framework; 18. a service manager; 19. a sub-interface module; 20. dynamic microservice; 21. resident microservice; 22. uplink data; 23. downlink data; 24. an original data module; 25. a standard data module; 26. a standard data interface; 27. a first service management module; 28. a second service management module; 29. and a third service management module.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1-8, in an embodiment of the present invention, a mechanism for reducing a software coupling degree through a software-based data interaction bus includes a data interaction bus 5, a standardized message 1, a subscriber 7, a publisher 10, an uplink data 22, a downlink data 23, and a generic development framework 17 formed based on the mechanism, and is characterized in that: the universal development framework 17 comprises a publisher 10, a service manager 18, a data interaction bus 5, a connection module 6 and a subscriber 7, wherein the output end of the publisher 10 is connected with the input end of the data interaction bus 5, the publisher 10 and the service manager 18 are connected in a bidirectional mode, the subscriber 7 and the connection module 6 are connected in a bidirectional mode, and the output end of the connection module 6 is connected with the input end of the data interaction bus 5.
Preferably, the data interaction bus 5 is respectively connected with the connection module 6 and the service management module 9 in two directions, the connection module 6 is connected with the subscriber 7 in two directions, the subscriber 7 is connected with the data display module 8 in two directions, and the service management module 9 is connected with the publisher 10 in two directions.
Preferably, the output of standardized message 1 is coupled to the input of interprocess scope 2, the output of interprocess scope 2 is coupled to the input of in-process scope 3, the output of in-process scope 3 is coupled to the input of inter-network scope 4, and the output of inter-network scope 4 is coupled to the input of standardized message 1.
Preferably, the input end of the inter-process scope 2 is connected to the output ends of the connection module one 61 and the service management module one 27, respectively, the output end of the connection module one 61 is connected to the input end of the subscriber module one 71, and the output end of the service management module one 27 is connected to the input end of the publisher module one 101.
Preferably, the input end of the in-process scope 3 is connected to the output ends of the second connection module 62 and the third service management module 29, the output end of the second connection module 62 is connected to the input end of the second subscriber module 72, and the output end of the third service management module 29 is connected to the input end of the third publisher module 103.
Preferably, the input end of the inter-network scope 4 is connected to the output ends of the connection module three 63 and the service management module two 28, the output end of the connection module three 63 is connected to the input end of the subscriber module three 73, and the output end of the service management module two 28 is connected to the input end of the publisher module two 102.
Preferably, the data interaction bus 5 and the data synchronization interface call 11 realize bidirectional connection, the data synchronization interface call 11 respectively realizes bidirectional connection with the subscriber 7 and the publisher 10, the data interaction bus 5 and the interface (attribute, method, notification) 12 realize bidirectional connection, the interface (attribute, method, notification) 12 respectively realizes bidirectional connection with the data subscription/request 13 and the data publication/notification 14, the data subscription/request 13 and the data display module 8 realize bidirectional connection, the data publication/notification 14 respectively realizes bidirectional connection with the service logic 16 and the life cycle management 15, and various services provided by the publisher 10 can be managed and scheduled through service life cycle.
Preferably, the upstream data 22 includes an output end of the data display module 8 connected to an input end of the subscriber 7, an output end of the subscriber 7 connected to an input end of the connection module 6, an output end of the original data module 24 connected to an input end of the publisher 10, an output end of the publisher 10 connected to an input end of the standard data module 25, an output end of the standard data module 25 connected to an input end of the standard data interface 26, and output ends of the standard data interface 26 and the connection module 6 connected to an input end of the data interaction bus 5, in the bus-based publishing and subscribing relationship, the publisher 10 and the subscriber 7 are completely independent, similar to a black box, and cannot sense the existence of external logic, the data stream is transmitted on the bus through the standard data interface 26 through a standard service, the publisher 10 finishes data collection and packages the data into standard data (attributes, method, notify), publish data on the bus through the standard data interface 26, wait for the subscription of the subscriber 7, when there is an update on the underlying data, the bus provides a data synchronization mechanism to synchronize the latest data.
Preferably, the downlink data 23 includes that the output end of the subscriber 7 is connected with the input end of the connection module 6, the output end of the connection module 6 is connected with the output end of the data interaction bus 5 and the input end of the publisher 10, the subscriber requests the downlink data to the bus by using a standard interface calling method of the bus, and the bus then requests the publisher to complete the downlink data.
Preferably, the input terminal of the generic development framework 17 is connected to the output terminal of the sub-interface module 19, and the output terminal of the generic development framework 17 is connected to the input terminals of the dynamic microservice 20 and the resident microservice 21, respectively.
The working principle of the invention is as follows:
when the data interaction system is used, a publisher 10 collects and centrally arranges original data, the publisher 10 collects and packages the data into a standard data interface (attribute, method and notification), the data are published on a data interaction bus 5 through the standard data interface, subscription of a subscriber 7 is waited, when bottom data is updated, the data interaction bus 5 provides a data synchronization mechanism to synchronize the latest data, the subscriber 7 calls the data interaction bus 5 through the standard interface of a bus 18 to request downlink data to the data interaction bus 5, the data interaction bus 5 then sends the request to the publisher 10, various services provided by the publisher 10 can be managed and scheduled through a service life cycle 15, in the publishing relation based on the data interaction bus 5, the publisher 10 and the subscriber 7 are completely independent and similar to a black box and cannot sense the existence of external logic, data streams are transmitted on the data interaction bus 5 through the standard data interface 26 through the standard service, from the perspective of top-level design, the data interaction bus 5 is a standard-based publish-subscribe design mode, conforms to the specification definition of the publish-subscribe mode, realizes and encapsulates the publisher 10 and the subscriber 7, and simultaneously increases the discovery, connection, scheduling and management of the service manager 18 as a dynamic service, the data interaction bus 5 is used as a data interaction channel to transmit standard formatted data, the data interaction bus 5 is used as an isolation zone to completely and physically isolate the publisher 10 and the subscriber 7, so that the publish and the subscribe are independent of each other and do not sense the existence of each other, the two associations are communicated through a standard interface provided by the data interaction bus 5, from the perspective of intra-module optimal coupling, the data between the publisher 10 and the subscriber 7 adopt a standardized data format, the communication type is determined by the scope of the data interaction bus 5, the interaction protocol is negotiated and formulated by a publisher 10 and a subscriber 7, the publisher 10 and the subscriber 7 perform data interaction externally through three data interface types of standard attributes, standard methods and standard notification, the publisher 10 and the subscriber 7 are realized according to the above definitions, and simultaneously, the publisher 10 and the subscriber 7 can interact with each other through a data interaction bus 5 between the publisher 10 and the publisher 10, and the design can disassemble a complex business logic 16 with high coupling degree into a plurality of micro-services with low coupling degree of fine grain, so that the coupling degree of the business logic inside the module is reduced on the basis of not reducing software functions, the reusability of the business is increased, the maintainability and the development complexity are reduced.
Although the present invention has been described in detail with reference to the foregoing embodiments, it will be apparent to those skilled in the art that various changes in the embodiments and/or modifications of the invention can be made, and equivalents and modifications of some features of the invention can be made without departing from the spirit and scope of the invention.
Claims (10)
1. A mechanism for reducing software coupling degree through a software-type data interaction bus comprises a data interaction bus (5), standardized messages (1), subscribers (7), publishers (10), connection modules (6), a service manager (18) and a general-purpose development framework (17) formed based on the mechanism. The method is characterized in that: the universality development framework (17) comprises the publisher (10), a service manager (18), the data interaction bus (5), a connection module (6), the subscriber (7) and a data display module (8), the output end of the publisher (10) is connected with the input end of the data interaction bus (5), the publisher (10) and the service manager (18) are in bidirectional connection, the subscriber (7) and the connection module (6) are in bidirectional connection, and the output end of the connection module (6) is connected with the input end of the data interaction bus (5).
2. The mechanism of claim 1, wherein the mechanism for reducing the software coupling degree via the software-based data interaction bus comprises: the data interaction bus (5) is respectively in bidirectional connection with the connection module (6) and the service management module (18), the connection module (6) is in bidirectional connection with the subscriber (7), the subscriber (7) is in bidirectional connection with the data display module (8), and the service management module (9) is in bidirectional connection with the publisher (10).
3. The mechanism of claim 1, wherein the mechanism for reducing the software coupling degree via the software-based data interaction bus comprises: the standardized messages (1) can interact within an in-process scope (3), can be expanded to an inter-process scope (2) interaction, and can be expanded to an inter-network scope (4) interaction.
4. The mechanism of claim 3, wherein the mechanism for reducing the software coupling degree via the software-based data interaction bus comprises: the input end of the interprocess scope (2) is respectively connected with the output ends of the connection module I (61) and the service management module I (27), the output end of the connection module I (61) is connected with the input end of the subscriber module I (71), and the output end of the service management module I (27) is connected with the input end of the publisher module I (101).
5. The mechanism of claim 3, wherein the mechanism for reducing the software coupling degree via the software-based data interaction bus comprises: the input end of the scope (3) in the process is respectively connected with the output ends of the second connection module (62) and the third service management module (29), the output end of the second connection module (62) is connected with the input end of the second subscriber module (72), and the output end of the third service management module (29) is connected with the input end of the third publisher module (103).
6. The mechanism of claim 3, wherein the mechanism for reducing the software coupling degree via the software-based data interaction bus comprises: the input end of the inter-network scope (4) is respectively connected with the output ends of the third connecting module (63) and the second service management module (28), the output end of the third connecting module (63) is connected with the input end of the third subscriber module (73), and the output end of the second service management module (28) is connected with the input end of the second publisher module (102).
7. The mechanism of claim 1, wherein the mechanism for reducing the software coupling degree via the software-based data interaction bus comprises: the data interaction bus (5) and the data synchronization interface call (11) realize bidirectional connection, the data synchronization interface call (11) respectively realizes bidirectional connection with the subscriber (7) and the publisher (10), the data interaction bus (5) and the interface (attribute, method and notification) (12) realize bidirectional connection, the interface (attribute, method and notification) (12) respectively realizes bidirectional connection with the data subscription/request (13) and the data publishing/notification (14), the data subscription/request (13) and the data display module (8) realize bidirectional connection, and the data publishing/notification (14) respectively realizes bidirectional connection with the business logic (16) and the service management (15).
8. The mechanism of claim 1, wherein the mechanism for reducing the software coupling degree via the software-based data interaction bus comprises: the uplink data (22) comprises that the output end of the data display module (8) is connected with the input end of the subscriber (7), the output end of the subscriber (7) is connected with the input end of the connection module (6), the output end of the original data module (24) is connected with the input end of the publisher (10), the output end of the publisher (10) is connected with the input end of the standard data module (25), the output end of the standard data module (25) is connected with the input end of the standard data interface (26), and the output ends of the standard data interface (26) and the connection module (6) are connected with the input end of the data interaction bus (5).
9. The mechanism for reducing software coupling through software-based data interaction bus of claim 1, wherein: the downlink data (23) comprises the output end of the subscriber (7) connected with the input end of the connection module (6), and the output end of the connection module (6) connected with the output end of the data interaction bus (5) and the input end of the publisher (10).
10. The mechanism of claim 1, wherein the mechanism for reducing the software coupling degree via the software-based data interaction bus comprises: the input end of the universal development framework (17) is connected with the output end of the sub-interface module (19), and the output end of the universal development framework (17) is respectively connected with the input ends of the dynamic micro-service (20) and the resident micro-service (21).
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210201993.3A CN114579493A (en) | 2022-03-03 | 2022-03-03 | Mechanism for reducing software coupling degree through software type data interaction bus |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210201993.3A CN114579493A (en) | 2022-03-03 | 2022-03-03 | Mechanism for reducing software coupling degree through software type data interaction bus |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114579493A true CN114579493A (en) | 2022-06-03 |
Family
ID=81775556
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210201993.3A Pending CN114579493A (en) | 2022-03-03 | 2022-03-03 | Mechanism for reducing software coupling degree through software type data interaction bus |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114579493A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104486440A (en) * | 2014-12-25 | 2015-04-01 | 浪潮电子信息产业股份有限公司 | Cloud computing management software interaction method based on message bus |
| CN104954469A (en) * | 2015-06-19 | 2015-09-30 | 长沙廖氏软件科技有限公司 | Information exchange method for heterogeneous system |
| US10666712B1 (en) * | 2016-06-10 | 2020-05-26 | Amazon Technologies, Inc. | Publish-subscribe messaging with distributed processing |
| CN112527525A (en) * | 2020-12-11 | 2021-03-19 | 广州伊智信息科技有限公司 | Distributed event bus processing method based on message queue, terminal and medium |
| CN112911012A (en) * | 2021-02-07 | 2021-06-04 | 珠海市一微半导体有限公司 | Robot sensor data distribution and subscription system, chip and robot |
-
2022
- 2022-03-03 CN CN202210201993.3A patent/CN114579493A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104486440A (en) * | 2014-12-25 | 2015-04-01 | 浪潮电子信息产业股份有限公司 | Cloud computing management software interaction method based on message bus |
| CN104954469A (en) * | 2015-06-19 | 2015-09-30 | 长沙廖氏软件科技有限公司 | Information exchange method for heterogeneous system |
| US10666712B1 (en) * | 2016-06-10 | 2020-05-26 | Amazon Technologies, Inc. | Publish-subscribe messaging with distributed processing |
| CN112527525A (en) * | 2020-12-11 | 2021-03-19 | 广州伊智信息科技有限公司 | Distributed event bus processing method based on message queue, terminal and medium |
| CN112911012A (en) * | 2021-02-07 | 2021-06-04 | 珠海市一微半导体有限公司 | Robot sensor data distribution and subscription system, chip and robot |
Non-Patent Citations (1)
| Title |
|---|
| 沈鑫 等: "基于多源异构数据聚合技术的电力物联网设备全景信息构架模型研究与应用", 南方电网技术, vol. 10, no. 2, pages 1 - 4 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20150026022A1 (en) | Billing device and processing method | |
| CN113268319A (en) | Business process customization and distributed process scheduling method based on micro-service architecture | |
| US20230297362A1 (en) | Voice scene update method and device, terminal, server and system | |
| CN106325887B (en) | Service process management method based on Activiti | |
| CN106598751B (en) | Method and system for distributing events through event bus | |
| CN101739300A (en) | Method and system for inter-process communication of multimedia terminal | |
| US20080163269A1 (en) | Remote procedure call system, remote procedure call method, program for implementing remote procedure call system | |
| CN106254468B (en) | A kind of control system and method for intelligent back vision mirror | |
| CN102520936A (en) | Method for realizing sharing of Socket communication service on Android platform | |
| WO2019201340A1 (en) | Processor core scheduling method and apparatus, terminal, and storage medium | |
| CN114615096B (en) | Event-driven architecture-based telecommunication charging method, system and related equipment | |
| CN111478839A (en) | Physical bus and operating system decoupled distributed aviation communication system | |
| CN111813503A (en) | Micro-service application open system based on container cloud | |
| CN114579493A (en) | Mechanism for reducing software coupling degree through software type data interaction bus | |
| CN109683875B (en) | Application framework system of MVC (model view controller) pattern in distributed environment and method thereof | |
| CN107896242A (en) | One kind service sharing method and device | |
| CN101795237A (en) | Workflow integration method and device based on data exchange | |
| CN111858106A (en) | Method for setting attributes of QML (QML framework) extension control | |
| CN117130797A (en) | Event message spreading method based on micro-service registry | |
| KR20010027192A (en) | Method for processing message from communication system in pilot terminal | |
| CN115208956B (en) | Implementation method of block chain gateway | |
| CN113347028B (en) | Internet of things platform management system developed based on MQTT and RocktMQ | |
| CN114936098B (en) | Data transfer method, device, back-end equipment and storage medium | |
| CN115016954B (en) | Event message management method, electronic device and computer readable storage medium | |
| CN111240773A (en) | Method for connecting front end and back end of software |
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 |