I'm wondering about MongoDB. Have you tried it recently? It really improves with every release. We have a 20TB Mongo database and it's fast and problem free.
Also regarding the queues. In my personal experience a single RabbitMQ server with good hardware can easily handle 50GB a day.
We're stuck with it now, and I really wish we had used Postgres for biz data and Cassandra for the high volume non-relational data. They're just materialized views on-top of your event stream anyway.
It's working fine, thank you very much. Of course it has little to do with terrorism, but in the political theater one has to make excuses for the unwashed masses.
"It's just temporary" is one of the five famous last words (together with "it worked on my machine"). It can easily turn into one of those projects where someone just shoved in autoconf to turn them into a giant ball of IFDEFs so nobody really knows which combinations work.
Toggling also only makes sense for the cases where you don't change the structure of your data. So be careful, and make sure you have a plan if you decide to do it.
The one place I worked that used them, switches were not temporary. There were about 4000 of them last time I checked.
There was an advantage: if a bug popped up you possibly had a workaround immediately for the customer. Downside is you had no idea if that workaround would expose more bugs.
I'm wondering about MongoDB. Have you tried it recently? It really improves with every release. We have a 20TB Mongo database and it's fast and problem free.
Also regarding the queues. In my personal experience a single RabbitMQ server with good hardware can easily handle 50GB a day.