Just have Trident write directly to whatever datastore you want. Trident's ability to interact with external state is completely generic, and the auto-batching will let you make efficient use of whatever database you choose.
On Mon, Jan 12, 2015 at 6:27 PM, Raphael Hsieh <[email protected]> wrote: > Thanks for your replies. > Nathan do you have any suggestions for external datastores? How were you > envisioning the use case for this? Just to stick it into a memcache and > from there transfer the data to a different external datastore ? > > Thanks > > On Thu, Jan 8, 2015 at 12:49 PM, Nathan Marz <[email protected]> > wrote: > >> Trident typically processes just a few batches per second. Actually >> you'll get much better db performance through Trident than you typically >> would manually *because* of the batching (instead of lots of individual >> round trips). >> >> On Thu, Jan 8, 2015 at 2:12 PM, Raphael Hsieh <[email protected]> >> wrote: >> >>> Doing a persistentAggregate to an external datastore seems like a pretty >>> standard use case. However Storm/Trident processes so many batches every >>> second, there are not many databases that can keep up with that large >>> amount of read/write throughput. >>> >>> How have people been deciding to store their storm aggregations in a way >>> that external services might be able to access this data ? >>> >>> -- >>> Raphael Hsieh >>> >>> >>> >>> >> >> >> >> -- >> Twitter: @nathanmarz >> http://nathanmarz.com >> > > > > -- > Raphael Hsieh > > > -- Twitter: @nathanmarz http://nathanmarz.com
