src/main/java/io/reactivex/Flowable.java
@CheckReturnValue
    @BackpressureSupport(BackpressureKind.PASS_THROUGH)
    @SchedulerSupport(SchedulerSupport.NONE)
    public final Flowable<T> serialize() {
        return RxJavaPlugins.onAssembly(new FlowableSerialized<T>(this));
    }
@CheckReturnValue
    @BackpressureSupport(BackpressureKind.PASS_THROUGH)
    @SchedulerSupport(SchedulerSupport.NONE)
    public final Flowable<T> serialize() {
        return RxJavaPlugins.onAssembly(new FlowableSerialized<T>(this));
    }
Forces a Publisher's emissions and notifications to be serialized and for it to obey
<a href="http://reactivex.io/documentation/contract.html">the Publisher contract</a> in other ways.
<p>
It is possible for a Publisher to invoke its Subscribers' methods asynchronously, perhaps from
different threads. This could make such a Publisher poorly-behaved, in that it might try to invoke
{@code onComplete} or {@code onError} before one of its {@code onNext} invocations, or it might call
{@code onNext} from two different threads concurrently. You can force such a Publisher to be
well-behaved and sequential by applying the {@code serialize} method to it.
<p>
<img width="640" height="400" src="https://raw.github.com/wiki/ReactiveX/RxJava/images/rx-operators/synchronize.png" alt="">
<dl>
<dt><b>Backpressure:</b></dt>
<dd>The operator doesn't interfere with backpressure which is determined by the source {@code Publisher}'s backpressure
behavior.</dd>
<dt><b>Scheduler:</b></dt>
<dd>{@code serialize} does not operate by default on a particular {@link Scheduler}.</dd>
</dl>

@return a {@link Publisher} that is guaranteed to be well-behaved and to make only serialized calls to
its Subscribers
@see <a href="http://reactivex.io/documentation/operators/serialize.html">ReactiveX operators documentation: Serialize</a>