This library provides a host for distributing change feed events in partitioned collection across multiple observers. Instances of the host can scale up (by adding) or down (by removing) dynamically, and the load will be automatically distributed among active instances in about-equal way.
The readme mentions partitions several times. However. it never makes clear whether the change feed processor leases physical or logical partitions.
(This is relevant in scenarios where multiple readers are used for performance reasons. For instance, if there are thousands of small logical partitions, all residing in the same physical partition, adding more change feed processing workers won't speed up things.)
So, would you please clarify that in the documentation?
(The city name ranges seem to indicate physical partitions, but it'd be nice to be sure.)
The readme mentions partitions several times. However. it never makes clear whether the change feed processor leases physical or logical partitions.
(This is relevant in scenarios where multiple readers are used for performance reasons. For instance, if there are thousands of small logical partitions, all residing in the same physical partition, adding more change feed processing workers won't speed up things.)
So, would you please clarify that in the documentation? (The city name ranges seem to indicate physical partitions, but it'd be nice to be sure.)