?I prefer (2) since it makes devops easier. The scaling and monitoring of a CPU intensive bolt (processing)is different from I/O bound bolt(persistence).
________________________________ From: Hemanth Yamijala <[email protected]> Sent: Wednesday, January 7, 2015 3:14 PM To: [email protected] Subject: Storm patterns vis-a-vis external data storage Hi all, I guess it is common to build topologies where message processing in storm results in data that should be stored in external stores like NoSQL DBs or message queues like Kafka. There are two broad approaches to handle this storage: 1) Inline the storage functionality with the processing functionality - i.e. the bolt generating the info to be stored also takes care of storing it. 2) Separate out the two and make a downstream bolt responsible for the storage. Just wanted to see if people on the list think if there are advantages to favour one approach over the other. Any pitfalls to take care of in one case over the other. Thanks Hemanth
