title: Parallel Flux vs Flux in project Reactor
body: <p>So what I have understood from the docs is that parallel Flux is that essentially divided the flux elements into separate rails.(Essentially something like grouping). And as far as thread is considered, it would be the job of schedulers. So let's consider a situation like this. And all this will be run on the same scheduler instance provided via runOn() methods.
  Let's consider a situation like below:</p>
  <pre><code>Mono&lt;Response&gt; = webClientCallAPi(..) //function returning Mono from webclient call
  </code></pre>
  <p>Now let's say we make around 100 calls</p>
  <pre><code>Flux.range(0,100).subscribeOn(Schedulers.boundedElastic()).flatMap(i -&gt; webClientCallApi(i)).collecttoList() // or subscribe somehow
  </code></pre>
  <p>and if we use paralleFlux:</p>
  <pre><code>Flux.range(0,100).parallel().runOn(Schedulers.boundedElastic()).flatMap(i -&gt; webClientCallApi(i)).sequential().collecttoList();
  </code></pre>
  <p>So if my understanding is correct, it pretty much seems to be similar. So what are the advantages of ParallelFlux over Flux and when should you use parallelFlux over flux?</p>