Unless you care about the 'state' of the batches after posting them to the API, the aggregator is simpler.
From: Flint, Ben [mailto:[email protected]] Sent: Thursday, November 20, 2014 2:02 PM To: [email protected] Subject: Aggregator or State for posting bulk events? All, I have a topology that decorates ad click events before POSTing them to a REST API for collection. The API accepts batches of events in a single call. What I am wondering is whether it would make more sense to use a Trident Aggregator that would build a list of events and POST them on complete(), or would it be better to create a Trident State that would POST to the API when it persists the batch state? Could someone offer some guidance here? -Ben ---------------------------------------------------------------------- This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.bankofamerica.com/emaildisclaimer. If you are not the intended recipient, please delete this message.
