Storm official documentation usage wizard

Storm official documents are divided into several parts:

The first part is an introduction to storm. It involves four sub-items: Preface, usage tutorial, Environment installation, and engineering example.

The second part focuses on some topics and provides an in-depth explanation of some core content of the storm framework. Therefore, the first part involves three sub-items: User Guide, Java Doc, and FAQ.

The third part describes how to get help from the community.

The fourth part introduces the surrounding ecology of storm.

For the first two parts, we will introduce them separately later, this article focuses on how to make full use of community resources to solve problems we encounter during daily use, use the mail list to track Storm Evolution, participate in community discussions, and the surrounding ecology of storm.

I. How to use the Community

The previous Google discussion group account ([email protected]) has been officially removed, and now uses the Apache mail list.

The use of the mail list can be divided into two types: common users and developers:

A common user can send an email to [email protected] and subscribe to its information. The specific subscription method is to send an email to [email protected] to subscribe to storm information. Likewise, send an email to [email protected] to cancel the subscription. You can alsoClick hereAccess archive information.

For developers, the address for sending mail and subscription information is [email protected]. The specific subscription method is similar to that for common users, but the address is changed to [email protected]. Similarly, the address for canceling mail is changed: [email protected] storm.incubator.apache.org. Archive list pleaseClick hereAccess.

For our daily users, how should we choose? The method is very simple, as follows:

1. If you are using a constructed binary package, you should send questions, comments, and storm-related announcements to [email protected.

2. If you use the source code to build storm, develop new features, or revise the patches for storm source code, [email protected] is more suitable.

Ii. surrounding Ecology

1. Storm-contrib: Various extension plug-ins developed based on storm, such as storm-Kafka and storm-hbase.

2. Storm-deploy: as the name suggests, one-click storm Installation Tool Based on the AWS Environment

3. spout implementations: Various spout implementations

4. dsls and multilang adapters: Domain Modeling Language and multi-language adaptation. Common examples include Scala, PHP, clojure, Esper, etc.

5. serializers: Various storm-based serialization implementations