There are rate limits (per user) on the Dropbox side, but they're pretty high. I think the bigger concurrency issue is going to be on your end (making sure you don't process the same changes multiple times). Taking a lease per-user is a good start, and we're going to publish a more advanced sample in the coming weeks that uses a queue to really eliminate duplicate calls.
Comments
Take a look at https://www.dropbox.com/developers/webhooks/tutorial#best-pr..., specifically the part about managing concurrency.
There are rate limits (per user) on the Dropbox side, but they're pretty high. I think the bigger concurrency issue is going to be on your end (making sure you don't process the same changes multiple times). Taking a lease per-user is a good start, and we're going to publish a more advanced sample in the coming weeks that uses a queue to really eliminate duplicate calls.