Storm-source code analysis summary

Storm-source code analysis summary storm features

Storm Introduction

Storm topology concurrency

Storm-guaranteeing Message Processing

Storm-transactional-Topologies

Twitter storm-DRPC

Storm multi-language support

 

Storm starter

Storm starter-Overview

Storm starter-singlejoinexample

Storm starter-rollingtopwords

 

Storm Topology

Storm-source code analysis-topology submit-Client

Storm-source code analysis-topology submit-Nimbus

Storm-source code analysis-topology submit-Nimbus-MK-assignments

Storm-source code analysis-relationships among component, executor, and tasks

Storm-source code analysis-Scheduler

Storm-source code analysis-topology submit-Supervisor

Storm-source code analysis-topology submit-worker

Storm-source code analysis-topology submit-executor

Storm-source code analysis-topology submit-executor-MK-threads

Storm-source code analysis-topology submit-task

Storm-source code analysis-topology submit-task-topologycontext (backtype. Storm. Task)

 

Storm modules

Storm-source code analysis-messaging (backtype. Storm. messaging)

Storm-source code analysis-streaming grouping (backtype.storm.daemon.exe cutor)

Storm-source code analysis-hook (backtype. Storm. Hooks)

Storm-source code analysis-Stats (backtype. Storm. Stats)

Storm-source code analysis-Metric

Storm-source code analysis-Acker (backtype. Storm. daemon. Acker)

 

Utils used in storm (can be used independently)

Storm-source code analysis-Use of Thrift

Storm-source code analysis-Use of zookeeper in Storm

Storm-source code analysis-Use of disruptor in Storm

Storm-source code analysis-localstate (backtype. Storm. utils)

Storm-source code analysis-timer (backtype. Storm. Timer)

Storm-source code analysis-eventmanager (backtype. Storm. Event)

Storm usage, bolt and spout

Storm-source code analysis-spout (backtype. Storm. spout)

Storm-source code analysis-bolt (backtype. Storm. Task)

 

Storm-source code analysis summary