Vector implements a concurrency model that scales naturally with incoming data volume as shown above. Each Vector source is responsible for defining the unit of concurrency and implementing it accordingly. This allows for a natural concurrency model that adapts to however Vector is being used, avoiding the need for tedious concurrency tuning and configuration.
As covered in the pipeline model documentation, Vector’s concurrency relies on stateless function transforms that can be inlined at the source level. Task transforms should thus be defined at the end of your topology to allow for maximum transform inlining.