Dynamic Topologies vs Fine-grained topologies in Apache Storm -

quick background:
customer can have multiple event processors (actions taken on particular input) , each of these event processors changed independently.
as optimization have grouped processors single customer single topology. advantage isolation across customers , on flip side entire topology customer needs redeployed if single processor changed, plus downtime takes kill topology , redeploy new topology.

now options contemplating is:

1. dynamic topology: no easy way change spouts , bolts @ runtime. storm swap doesn't seem available yet. there way dynamically update topologies without deployment or way hot deploy topologies.
2. have 1 topology per event processor per customer. end having thousands or 100 thousand topologies , seems incorrect.

have read through this old post, not of help. whats recommendation.