CN110263282A - A kind of design method of the content distribution subscription communication pattern based on Kafka - Google Patents
A kind of design method of the content distribution subscription communication pattern based on Kafka Download PDFInfo
- Publication number
- CN110263282A CN110263282A CN201910530336.1A CN201910530336A CN110263282A CN 110263282 A CN110263282 A CN 110263282A CN 201910530336 A CN201910530336 A CN 201910530336A CN 110263282 A CN110263282 A CN 110263282A
- Authority
- CN
- China
- Prior art keywords
- kafka
- design
- distribution subscription
- subscription
- 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.)
- Withdrawn
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- 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/546—Message passing systems or structures, e.g. queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/548—Queue
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The design method of the invention proposes a kind of content distribution subscription communication pattern based on Kafka, the following steps are included: step (1): according to the functional characteristics of distributed stream processing platform Kafka, in conjunction with the objective demand of the distribution subscription system based on content, the member node and topological structure of the communication pattern are designed;Step (2): on the basis of step (1), specifically design the interaction mechanism and correlation distribution subscription process of each member node, the present invention by addition agent node and redesigns communication process on the basis of the publish-subscribe model based on theme that Kafka platform has to realize the publish-subscribe model based on content for possessing more high rule complexity.
Description
Technical field
The present invention relates to a kind of communication pattern, specifically a kind of communication pattern design method belongs to communication technology neck
Domain.
Background technique
Distribution subscription system is a kind of system for carrying out message distribution with distribution subscription communication pattern, is generally gathered around in the system
There are three types of roles, are respectively: the producer (i.e. publisher) of message, the consumer (i.e. subscriber) of message and Message Agent.
Publisher will need the information transmitted to be sent to distribution subscription Message Agent;Subscriber registers in distribution subscription Message Agent and orders
It reads, it is interested in which kind of information that subscription describes the subscriber;Distribution subscription Message Agent is responsible for sending the producer
The information come is passed to the interested subscriber of the information.
Distribution subscription communication pattern is divided into according to the power of description ability to express: distribution subscription system, base based on pipeline
Distribution subscription system in theme, the distribution subscription system based on content, the distribution subscription system based on type, and distribution subscription
The power of system expression information capability is directly proportional to the power of description subscriber's interest ability.Academia and industry are for publication
It subscribes to communication pattern and has carried out many practices, academia focuses more on the ability to express of system, and industry then focuses more on practical
Property.Kafka stream process platform is one of Typical Representative of industry, which possesses brilliant fault-tolerant ability, data throughput energy
Power, horizontal extension ability, but only have the distribution subscription communication function based on theme, ability to express is weaker.Based on the above reasons,
The invention is intended to promote the ability to express of Kafka platform.
Summary of the invention
The design method of the object of the present invention is to provide a kind of content distribution subscription communication pattern based on Kafka, makes it
Can the content of the subscription condition based on subscriber and event carry out fine-grained match messages and distribution.
The object of the present invention is achieved like this: a kind of design side of the content distribution subscription communication pattern based on Kafka
Method, comprising the following steps:
Step (1): according to the functional characteristics of distributed stream processing platform Kafka, in conjunction with the distribution subscription system based on content
Objective demand designs the member node and topological structure of the communication pattern;
Step (2): on the basis of step (1), the interaction mechanism and correlation distribution subscription process of each member node are specifically designed.
It is further limited as of the invention, in step (1), the design of member node and topological structure includes following step
It is rapid:
Step (1.1): it is set in conjunction with objective demand and the characteristics of Kafka distribution subscription function of the distribution subscription system based on content
Count new agent node;
Step (1.2): according to the universal model of distribution subscription communication system, in conjunction with the agency's section proposed in step (1.1)
Point designs the topological structure of the communication pattern.
Further limited as of the invention, in step (2), each member node interaction flow it is specific design include with
Lower step:
Step (2.1): the interactive mode of design agent node and agent node and agent node and Kafka cluster;
Step (2.2): the design producer issues the process of event;
Step (2.3): the process that design subscriber's registration is subscribed to deletion;
Step (2.4): design Kafka cluster and agent collaborative carry out event-subscribing matching process.
It is further limited as of the invention, in step (2.3), subscriber's registration is specific with the process of deletion subscription
Design includes: to design subscriber to register the specific steps subscribed to, and design subscriber deletes the specific steps subscribed to, and design generation
Manage the index structure that node storage is subscribed to.
Compared with prior art, the beneficial effects of the present invention are: in existing distributed stream platform kafka integrate hair
Cloth subscribes to the publication and subscription that function only supports the message of subject-oriented, and the present invention is by definition agent node, and seals again
Dress publication subscribes to related procedure to enhance the ability to express of distribution subscription function in kafka, allows to for the specific of message
Content executes relevant operation, while the advantage for retaining kafka itself.
Detailed description of the invention
Fig. 1 is ordering system concept structure figure in the present invention.
Fig. 2 is problem transformation result schematic diagram in the present invention.
Fig. 3 topology diagram of the present invention.
Fig. 4 is attribute a in the present invention1Lower limit barrel chain.
Fig. 5 is attribute a in the present invention1Upper limit barrel chain.
Fig. 6 is attribute a in the present invention2Lower limit barrel chain.
Fig. 7 is attribute a in the present invention2Upper limit barrel chain.
Specific embodiment
Technical solution of the present invention is described in further detail with reference to the accompanying drawing:
A kind of design method of the content distribution subscription communication pattern based on Kafka is right in the following with reference to the drawings and specific embodiments
The present invention is described in further detail.
Step (1): according to the functional characteristics of distributed stream processing platform Kafka, in conjunction with the distribution subscription system based on content
The objective demand of system designs the member node and topological structure of the communication pattern;The step is divided into two small steps.
First small step, i.e. step (1.1) need to combine the objective demand of the distribution subscription system based on content and Kafka to send out
Cloth subscribes to the characteristics of function and designs new agent node:
Each event e is the set of a key-value pair in distribution subscription system based on content, and each key-value pair is by keyword
(Key), it is worth (Value composition), a key-value pair A can be indicated are as follows:
A = A(Key, Value)
Therefore the set e of key-value pair can be expressed as e={ A1, A2, A3,…, An, the collection of all keywords is collectively referred to as in system
For the property set A of the distribution subscription systemS, ASIn each attribute be owned by its codomain.
Based on the structure of above-mentioned event, subscriber limits category by predicate set s composed by one or several predicates
Property set ASIn all or part of attribute, the interest of oneself is expressed with this, each predicate P is by keyword (Key), operator
(Operator), three kinds of value (Value) is at being grouped as, wherein operator can for >, <, >=,≤, then a predicate can be with table
It is shown as:
P = P(Value, Operator, Key, Operator, Value)
Therefore a subscription can indicate are as follows:
s = { P1, P2, P3,…, Pn }
If existing attribute set AS = {a1, a2, and a1∈[0, 10], a2∈ [0,10], then the producer of information can produce
Make trouble part e={ a1 = 5, a2=10 }, subscriber can subscribe to s={ 5 >=a by registration1 >= 6, 7 >= a2 >=
8 } oneself interest is expressed.
Structure based on above-mentioned event and subscription, if event e matches with s is subscribed to, for subscribing to each predicate P in s
The attribute constraint of defined, the value that attribute is corresponded in event e can meet the constraint, i.e. attribute value in event e can satisfy
Subscribe to predicate constraint all in s;At least there is the constraint of predicate in s if subscribed to, in event e without corresponding attribute value or
The value of corresponding attribute is unable to satisfy the constraint, then claims event e and subscribe to s mismatch.
Based on above-mentioned event-subscribing matching principle, matching problem can be converted into rectangle intersection problem and ordered with simplifying event-
Read matching process.Detailed process is as follows for conversion:
(1) by system property set AsThe codomains of middle all properties expands twice (such as will belonging to originally property a1Codomain [0,10] expand
Transform into [0,20]);
(2) boundary for the predicate constraint for being included by the subscription of all incoming systems expands twice of formation space rectangle (such as by 5
>= a1>=6 are extended to 10 >=a1>=12);
(3) value of the attribute in the event of all incoming systems is first expanded twice, using being extended to sky after adding 1 operation that subtracts 1
Between rectangle (such as by event e={ a1 = 3, a2=4 } it is extended to { 5 >=a1 >= 7, 7 >= a2>=9 });
After above-mentioned extended operation, event-subscribing matching problem can be converted into space rectangle intersection problems, such as judgement is ordered
Read s={ 2 >=a1 >= 5, 6 >= a1>=8 } and event e={ a1= 5, a2=6 } rectangular { 4 >=a can be changed1
>= 10, 12 >= a2>=16 } and rectangle { 9 >=a1 >= 11, 11 >= a2>=13 }, it is specific as shown in Figure 2.
Composed structure based on above-mentioned event and subscription, feels it if distribution subscription node is want for event to be accurately transmitted to
The subscriber of interest needs with subscription condition to be matched the particular content of event one by one, and is determined according to matching result
Specific forwarding object, and the distribution subscription function based on theme provided by Kafka stream process platform can only will stamp theme
Each event forwarding of label gives the subscriber for having subscribed the theme, but can not carry out more particulate based on the particular content of the event
The screening of degree, it is therefore desirable to design agent node on the basis of Kafka original function, which possesses following function:
(1) normal communication can be carried out with Kafka platform, event is received from platform or sends event to platform;
(2) subscription condition, can be converted into theme, and create the theme to forward by the subscription condition of storage subscriber publication
Event;
(3) event is transmitted to by corresponding theme to the interested subscription of the event by the event for matching incoming Kafka platform
Person;
The distribution subscription function based on theme is converted to the distribution subscription function based on content by the agent node, is made
Kafka platform possesses more powerful ability to express.
Second small step, i.e. step (1.2) need the universal model according to distribution subscription communication system, in conjunction with step
(1.1) agent node proposed in, designs the topological structure of the communication pattern:
The conceptual model of distribution subscription system is as shown in Figure 1, generally comprise: publisher, subscriber and distribution subscription node;Publication
The communication network for subscribing to distribution subscription cluster composed by node (being herein Kafka cluster) is generally reticular structure, with
The robustness of raising system prevents whole system from paralysing because of the damage of a small amount of node.The agent node in conjunction with described in upper step, it is whole
A communication system is made of four parts, is agency's collection composed by publisher, subscriber, Kafka cluster and agent node respectively
Group, it is wherein mutually indepedent between publisher and publisher, between subscriber and subscriber and between publisher and subscriber,
Without knowing mutual presence, any publisher or subscriber need to only communicate with Kafka cluster;Kafka cluster is big by two
Part forms, and is Kafka node and zookeeper node respectively, wherein zookeeper node is in reticular structure group between each other
At zookeeper cluster, each Kafka node is general only need to be with zookeeper cluster communication;Agent cluster is also in netted knot
Structure, each agent node knows mutual presence, while each agent node can be communicated individually with Kafka cluster, the communication system
The topological structure of system is specifically as shown in Figure 3.
Step (2): on the basis of step (1), the interaction flow and event-subscribing matching of each member node are specifically designed
Mechanism;The step specifically includes 4 small steps.
First small step, step (2.1) need to design agent node and agent node and agent node and Kafka cluster
Interactive mode:
Distribution subscription function based on Kafka possesses the advantages that zmodem, data throughput capabilities are strong, horizontal extension ability is strong,
But it still belongs to the distribution subscription classification based on theme, and ability to express is more weak, can not identify subscription, can not be according to event
Content Selection event, therefore devise agent node herein with store subscribe to, subscribed to according to the content matching of event and complete phase
The forwarding operation answered.
In conclusion agent node both needs to receive event and subscription condition in incoming Kafka cluster, at the same need by
The event forwarding gives the subscriber to match, therefore needs two themes to distinguish when agent node and Kafka cluster interact
To receive information and send information.Due to needing to make full use of the computing resource of agent node, while bottleneck is not formed, thus it is every
A agent node is relatively independent to the theme for receiving/sending information;Therefore each agent node possesses only in Agent cluster
One ID registers exclusive reception/transmission information theme to indicate itself with the ID, and name format is as follows:
Receive the theme of information: proxy_receive_ID, send the theme of information: proxy_send_ID,
Two themes as above are just created when being added cluster in new agent node, and monitor proxy_receive_ID, whenever
Just two themes as above are deleted when agent node exits cluster.Also connection can be established between each agent node subscribes to letter with shared
Breath.
Second small step, i.e. step (2.2) need the process of design issue person's publication event:
Since each event of publisher's publication requires to pass to agent node, the event is ordered with what is stored by agent node
Carry out matching operation is read, therefore publisher filters out firstly the need of the list for obtaining all themes in Kafka cluster with proxy_
The theme of receive beginning randomly chooses one of them later and sends event to the theme.Each publisher needs to safeguard simultaneously
The set E of one event to be sentsTo mark not sent or send failed event, by the thing if certain event is sent successfully
Part is rejected from set.
If there are multiple event waits to send by certain publisher, then when it randomly chooses a certain proxy_receive beginning
Theme and after completing the transmission of first event, successively select the theme of remaining proxy_receive beginning to complete residue
The transmission of event, while successful event will be sent from EsMiddle rejecting, if event number to be sent is greater than proxy_receive list
In number of topics, then recycle the theme in the list to continue the transmission task of event, until EsFor sky.
Third small step, i.e. step (2.3) need to design subscriber's registration and delete the process subscribed to:
The format of s is subscribed to shaped like s as described in step (1)={ P1, P2, P3,…, Pn , Pn+1, wherein predicate P1- Pn
To describe the interest of the subscriber, the last one predicate Pn+1Shaped like ID=subscriber ' ID, to indicate the subscription
Owner, therefore each subscriber need to possess the unique ID that can indicate its identity.
Since event-subscription matching is completed with forwarding work by agent node, therefore subscriber needs to pass subscription information
Pass agent node;Therefore all masters started when subscriber carries out subscription registration firstly the need of acquisition with proxy_receive
Topic, random selection wherein some, subscription is connect after keyword create_subscribe through the master after the completion of selection
Topic is sent to agent node, and the theme of message is sent while listening for agent node.Such as the desired registration of subscriber that ID is srk is ordered
Read s={ 5 >=a1 >= 6, 7 > a2> 8 }, and chosen ID for the master for being used to receive information of the agent node of pxk
Inscribe proxy_receive_pxk, then it will be to transmission subscription registration information create_subscribe={ 5 >=a under the theme1
>= 6, 7 > a2> 8, ID=srk }, and monitor proxy_send_pxk theme.
Each agent node will safeguard that subscriber's set registered ordering for subscription to store in a communications system
Reader and the subscriber are still in the number of the subscription used;Each agent node will also safeguard several barrel chains to index and subscribe to simultaneously
Information, the number of barrel chain are 2n, and wherein n is the property set A of systemsThe number of middle attribute.Each attribute need to construct two barrel chains,
Respectively represent the bound of the attribute.Constructing barrel chain, specific step is as follows:
(1) codomain of each attribute is divided into multiple units, each unit corresponds to a bucket, all values in the unit
All map to the bucket;
(2) when the predicate constraint consistency in subscription is to some barrel, the index of the subscription and subscriber ID are inserted into the bucket.
It is now assumed that property set As = {a1, a2, a1With a2Codomain be all [0,10], and have subscription list as follows:
Based on above- mentioned information building barrel chain firstly the need of carrying out dividing elements respectively to each attribute value to construct the bucket of its bound
Chain, due to attribute a1, a2Codomain be all [0,10], its codomain is respectively classified into 4 units, each unit pair after extension
A bucket is answered, totally 16 buckets are subscribed to for indexing;Then it is inserted into corresponding bucket, such as subscribed to according to the constraint of the predicate of subscription
s0Middle attribute a1Value range be [0,2] after extension, therefore by s0It is inserted into a1Unit [0,5] and a in codomain upper limit barrel chain1
In codomain lower limit barrel chain in the corresponding bucket of unit [0,5].Barrel chain is obtained as shown in figs. 4-7 after all subscription insertions.
Fig. 4 and Fig. 5 indicates attribute a1Lower limit barrel chain and upper limit barrel chain, Fig. 6 and Fig. 7 indicate attribute a2Lower limit barrel chain with
Upper limit barrel chain, each bucket represents a certain range of upper limit or lower limit in barrel chain, and the subscription mapped in the range can be inserted into
It in corresponding bucket, while being inserted into the index of subscription and the ID of subscriber and can also be stored in bucket, such as after extension, order
Read s0-s5Middle attribute a1The upper limit be respectively 0,4,6,2,8,12, therefore s0, s1, s3It is stored in first bucket of Fig. 4, s2With s4It deposits
It is placed in second bucket of Fig. 4, s5It is stored in the third bucket of Fig. 4, the case where Fig. 5-7 is similar.
It now sets ID and receives subscription registration information create_subscribe={ 5 >=a as the agent node of pxk1 >=
6, 7 > a2> 8, ID=srk } after, following steps will be carried out:
(1) it is srk in the last one subscription condition i.e. subscriber ID(this example that pxk, which is intercepted), if srk is present in ordering for pxk maintenance
In reader's set, then by subscriber gather in the subscription of the subscriber add 1, and to the predicate P in subscription condition1-PnIt is asked
It again will be in the barrel chain that subscribe to insertion pxk maintenance after topic conversion;
(2) if srk is not present in px1In subscriber's set of maintenance, then new attribute, attribute-name are created in subscriber's set
For srk, attribute value 1;To the predicate P in subscription condition after the completion of assignment1-PnThe subscription, is inserted by carry out problem conversion later
In the barrel chain of pxk maintenance, and event forwarding channel is created using the ID of subscriber, the format of channel name (subject) is
Subscriber_ID, as subscriber_srk, all things for meeting srk interest are forwarded using the theme in this example
Part;
(3) pxk sends the successful message of subscription registration, message format into theme proxy_send_pxk are as follows:
subscribe_crreate_success = {ID: data}
Wherein subscribe_crreate_success is keyword, and to identify the purposes of this information, ID is to register this to order
The ID of the subscriber read, data be subscription information hash value, in this example as subscribe_crreate_success=
{srk: hashdata};Subscriber passes through data segment after receiving the message that subscribe_crreate_success starts
ID value screens message related with itself, and the subscription of successful registration is confirmed by hash value, is simultaneously stopped and monitors proxy_
Send_pxk theme;
(4) the subscription registration information received is passed to adjacent agent node by pxk;Adjacent agent node is ordered after receiving
The update of set is read, while the subscription registration information received is passed into remaining adjoining agent node of non-sourcing until entire
Agent node cluster is completed to subscribe to the update of set.
ID is now set to want to delete the subscription s={ 5 >=a once registered as the subscriber of srk1 >= 6, 7 > a2 > 8,
ID=srk }, following steps will be carried out:
(1) all themes started with proxy_receive in communication system are obtained, a certain theme are randomly choosed, to the theme
It sends to subscribe to and deletes message, the format of message are as follows:
subscribe_delete = {ID: data}
Wherein subscribe_delete is keyword, is subscribed to identify this information to delete, and ID is to delete the subscription
Subscriber ID, data be want delete subscription predicate set, it is assumed that choose agent node pxk in this example, then will
It sends to subscribe to theme proxy_receive_pxk and deletes message subscribe_delete={ srk:{ 5 >=a1 >=
6, 7 > a2> 8}};
(2) after agent node receives subscription deletion message, the subscriber that will traverse itself maintenance gathers, and finds out the subscriber simultaneously
Its subscription is subtracted 1;If subscription is 0 after reducing, which is deleted from subscriber's set, while from Kafka collection
Deleting in group and forwarding the theme of event to the subscriber (is subscriber_srk) in this example.It also needs to update bucket after reducing
Chain, by the record deletion in the barrel chain of agent node maintenance about the subscription;
(3) subscription received is deleted into message transmission to adjacent agent node after deleting successfully;Adjacent agent node receives it
It carries out subscribing to the update of set afterwards, while the subscription received is deleted into message transmission to remaining adjoining agent node of non-sourcing
Until entire agent node cluster is completed to subscribe to the update of set.
4th small step, i.e. step (2.4) need to design Kafka cluster and agent collaborative carries out event-subscribing matching stream
Journey now sets subscription node pxk and receives event e={ a1 = 6, a2=8 }, specific process flow is as follows:
(1) a position collection is initialized to indicate to subscribe to whether match, and position concentrates in binary digit number and system and subscribes to number
Equal, all positions are all 0 under the collection initial situation of position, and often finding out a unmatched subscription just will corresponding binary location 1;
(2) attribute value in event is subjected to problem conversion and is extended to space rectangle;
(3) value range of attribute in the rectangle of space is successively substituted into barrel chain and found out and meet the subscription of following property, position is concentrated
Corresponding binary location 1:
A, the value upper limit of the subscription attribute is lower than the value lower limit of the space rectangle attribute;
B, the value lower limit of the subscription attribute is higher than the value upper limit of the space rectangle attribute;
(4) binary digit 0 subscription and its subscriber ID not yet are taken out, event is subscribed to these again and carries out matching operation,
Compare the constraint in attribute and the subscription in event to the attribute one by one, find out the subscription of exact matching, according to its subscriber
ID finds out corresponding subject (subscriber_ID), and event is transmitted to subscriber by the theme.
The above, the only specific embodiment in the present invention, but scope of protection of the present invention is not limited thereto, appoints
What is familiar with the people of the technology within the technical scope disclosed by the invention, it will be appreciated that expects transforms or replaces, and should all cover
Within scope of the invention, therefore, the scope of protection of the invention shall be subject to the scope of protection specified in the patent claim.
Claims (4)
1. a kind of design method of the content distribution subscription communication pattern based on Kafka, it is characterised in that: include the following steps,
Step (1): according to the functional characteristics of distributed stream processing platform Kafka, in conjunction with the distribution subscription system based on content
Objective demand designs the member node and topological structure of the communication pattern;
Step (2): on the basis of step (1), the interaction mechanism and correlation distribution subscription process of each member node are specifically designed.
2. a kind of design method of content distribution subscription communication pattern based on Kafka according to claim 1, feature
Be, in step (1), the design of member node and topological structure the following steps are included:
Step (1.1): it is set in conjunction with objective demand and the characteristics of Kafka distribution subscription function of the distribution subscription system based on content
Count new agent node;
Step (1.2): according to the universal model of distribution subscription communication system, in conjunction with the agency's section proposed in step (1.1)
Point designs the topological structure of the communication pattern.
3. a kind of design method of content distribution subscription communication pattern based on Kafka according to claim 1, feature
Be, in step (2), each member node interaction flow it is specific design the following steps are included:
Step (2.1): the interactive mode of design agent node and agent node and agent node and Kafka cluster;
Step (2.2): the design producer issues the process of event;
Step (2.3): the process that design subscriber's registration is subscribed to deletion;
Step (2.4): design Kafka cluster and agent collaborative carry out event-subscribing matching process.
4. a kind of design method of content distribution subscription communication pattern based on Kafka according to claim 1, feature
It is, in step (2.3), subscriber's registration includes: that design subscriber's registration is ordered with the specific design for deleting the process subscribed to
The specific steps read, design subscriber delete the specific steps subscribed to, and the index structure that design agent node storage is subscribed to.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910530336.1A CN110263282A (en) | 2019-06-19 | 2019-06-19 | A kind of design method of the content distribution subscription communication pattern based on Kafka |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910530336.1A CN110263282A (en) | 2019-06-19 | 2019-06-19 | A kind of design method of the content distribution subscription communication pattern based on Kafka |
Publications (1)
Publication Number | Publication Date |
---|---|
CN110263282A true CN110263282A (en) | 2019-09-20 |
Family
ID=67919360
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201910530336.1A Withdrawn CN110263282A (en) | 2019-06-19 | 2019-06-19 | A kind of design method of the content distribution subscription communication pattern based on Kafka |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN110263282A (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113992741A (en) * | 2020-07-10 | 2022-01-28 | 华为技术有限公司 | Method and device for publishing data index |
CN114844948A (en) * | 2021-12-14 | 2022-08-02 | 合肥哈工轩辕智能科技有限公司 | Client cache optimization method and device of real-time distribution system |
CN115794444A (en) * | 2023-02-02 | 2023-03-14 | 广州钛动科技股份有限公司 | Event communication method, device, computer equipment and computer readable storage medium |
-
2019
- 2019-06-19 CN CN201910530336.1A patent/CN110263282A/en not_active Withdrawn
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113992741A (en) * | 2020-07-10 | 2022-01-28 | 华为技术有限公司 | Method and device for publishing data index |
CN114844948A (en) * | 2021-12-14 | 2022-08-02 | 合肥哈工轩辕智能科技有限公司 | Client cache optimization method and device of real-time distribution system |
CN114844948B (en) * | 2021-12-14 | 2024-05-31 | 合肥哈工轩辕智能科技有限公司 | Client cache optimization method and device of real-time distribution system |
CN115794444A (en) * | 2023-02-02 | 2023-03-14 | 广州钛动科技股份有限公司 | Event communication method, device, computer equipment and computer readable storage medium |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7627611B2 (en) | Conflict resolution in database replication through autonomous node qualified folding | |
CN110263282A (en) | A kind of design method of the content distribution subscription communication pattern based on Kafka | |
CN111445328A (en) | Cross-link gateway interaction system and method and supply chain data management method | |
CN102724307B (en) | For information fusion engine and the method for Internet of Things | |
KR101304663B1 (en) | The system of cooperative editing of mind-map and the method thereof | |
CN109684287A (en) | Gateway information sharing query method and system based on block chain | |
CN104346377A (en) | Method for integrating and exchanging data on basis of unique identification | |
CN106933989A (en) | A kind of method of Web realease information system | |
CN107017992A (en) | A kind of high-performance alliance block chain based on duplex structure | |
CN111159755A (en) | Cross-link data cooperation method based on alliance link | |
CN108197138A (en) | The method and system for the matching subscription information that releases news in publish/subscribe system | |
CN105426307A (en) | Local area network product test resource sharing method and system | |
CN105930174B (en) | A kind of graphical page program comparison in difference method and system | |
CN102843310B (en) | Based on the issue of message in the wide area network of rumor agreement, method for subscribing and system | |
CN106131134A (en) | A kind of message content merges De-weight method and system | |
CN109995596A (en) | A kind of alliance's block chain visualization business partition method | |
CN105723365B (en) | Method for optimum indexing, main database node and subscriber database node | |
US6839749B1 (en) | Network representation and manipulation thereof | |
Zarzour et al. | srCE: a collaborative editing of scalable semantic stores on P2P networks | |
KR100971683B1 (en) | Representation method of feed relationship in design processes using interrelationship among parts | |
CN108173688A (en) | A kind of management method of the networking configuration content based on tree and version number | |
Isli et al. | A topological calculus for cartographic entities | |
CN105915376A (en) | Log information network structuring method and log information network structuring system based on P2P program requesting system | |
EP1111518A1 (en) | System and method for document notification and delivery across heterogeneous document repositories | |
JP2007279839A (en) | Database management system and table association method for relational database |
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 | ||
WW01 | Invention patent application withdrawn after publication |
Application publication date: 20190920 |
|
WW01 | Invention patent application withdrawn after publication |