Hi all,

I'm very new to apache-storm and I have to admit I don't have a lot of
experience with NoSQL in general either.

I'm modelling my data using a document-based approach and I'm trying to
figure out how to update versions of a (sub) document stored in different
"documents". It's the classic scenario where you store user's info in the
comments table. Updates to the user's name (for example) should be
propagated to all the comments.

My understanding is that in this scenario people would trigger a procedure
on the user's name update that scans all the related documents to update
the user's name.

I was considering using apache-storm to propagate updates and I would like
to have some feedback from more experienced developers on this kind of
problems.

Would apache-storm be too much? Should I just use zookeeper?

My understanding is that apache-storm is mostly used for complex data
manipulations and here all I need to do is to keep the data in sync for
consistency when accessed by users. Am I going the wrong direction? How do
you guys solve this kind of problems?

Thanks,
Michel

Reply via email to