Afterword

 

Congratulations, you’ve made it to the end of the book. Where do you go from here? The answer depends on how you got here. If you read the book from start to end, we suggest implementing your own topologies while referring back to various chapters until you feel like you’re “getting the hang of Storm.” We hesitate to say “mastering Storm” as we’re not sure you’ll ever feel like you’re mastering Storm. It’s a powerful and complicated beast, and mastery is a tricky thing.

If you took a more iterative approach to the book, working through it slowly and gaining expertise as you went along, then everything else that follows in this afterword is for you. Don’t worry if you took the start-to-end approach; this afterword will be waiting for you once you feel like you’re getting the hang of Storm. Here are all the things we want you to know as you set off on the rest of your Storm journey without us.

You’re right, you don’t know that

We’ve been using Storm in production for quite a while now, and we’re still learning new things all the time. Don’t worry if you feel like you don’t know everything. Use what you know to get what you need done. You’ll learn more as you go. Analysis paralysis can be a real thing with Storm.

There’s so much to know

Metrics and reporting

Trident is quite a beast

When should I use Trident?

Abstractions! Abstractions everywhere!