· Apache Kafka is an appropriated distribute subscribe informing framework publicly released by LinkedIn
· It accompanies straight versatility, elite and information is recreated and divided
· One must be inquiring as to why Kafka is in the outline when flume gives comparable usefulness
· Kafka will be utilized to connect the structural holes in the middle of Flume and Storm.
· Example of 3 holes why Kafka
o The Flume sink utilizes a push component for sending occasions, while Storm spout utilizes the an instrument for the occasions
o work submitted to Storm is known as a topology. Different phases of Storm topologies (MR sort employments) keeps running on distinctive hubs and Storm chiefs focus the hubs in the bunch to run diverse phases of a topology Essentially, the rundown of hubs where a specific topology will run is not known ahead of time
o The Flume sink utilizes a push system, subsequently it must know ahead of time where occasions should be pushed to, which is not the situation here
o In the POC, we didn't utilize Kafka as we added to a custom flume sink to push occasions specifically to Storm as just single hub bunch was being utilized. This is not going to work once the Storm bunch has more than one hub
· Kafka, then again, depends on the distribute subscribe programming worldview. Makers push messages and customers force messages. In our outline, there is a push framework (Flume) toward one side and force framework (Storm) on the flip side. Henceforth, Kafka is an impeccable answer for extension this hole and determines both issues said b
· It accompanies straight versatility, elite and information is recreated and divided
· One must be inquiring as to why Kafka is in the outline when flume gives comparable usefulness
· Kafka will be utilized to connect the structural holes in the middle of Flume and Storm.
· Example of 3 holes why Kafka
o The Flume sink utilizes a push component for sending occasions, while Storm spout utilizes the an instrument for the occasions
o work submitted to Storm is known as a topology. Different phases of Storm topologies (MR sort employments) keeps running on distinctive hubs and Storm chiefs focus the hubs in the bunch to run diverse phases of a topology Essentially, the rundown of hubs where a specific topology will run is not known ahead of time
o The Flume sink utilizes a push system, subsequently it must know ahead of time where occasions should be pushed to, which is not the situation here
o In the POC, we didn't utilize Kafka as we added to a custom flume sink to push occasions specifically to Storm as just single hub bunch was being utilized. This is not going to work once the Storm bunch has more than one hub
· Kafka, then again, depends on the distribute subscribe programming worldview. Makers push messages and customers force messages. In our outline, there is a push framework (Flume) toward one side and force framework (Storm) on the flip side. Henceforth, Kafka is an impeccable answer for extension this hole and determines both issues said b
No comments:
Post a Comment