static member Start<'M,'Res>
        (   log : ILogger, config : KafkaConsumerConfig, parseStreamEvents,
            prepare, handle, maxDop, stats : Streams.Scheduling.StreamSchedulerStats<OkResult<'Res>,FailResult>,
            /// Prevent batches being consolidated prior to scheduling in order to maximize granularity of consumer offset updates
            ?maximizeOffsetWriting,
            ?pipelineStatsInterval, ?maxSubmissionsPerPartition, ?pumpInterval, ?logExternalState, ?idleDelay)=
        Core.StreamsConsumer.Start<'M,(string*Propulsion.Streams.StreamSpan<_>),'Res>(
            log, config, Bindings.mapConsumeResult, parseStreamEvents, prepare, handle, maxDop, stats,
            ?pipelineStatsInterval = pipelineStatsInterval,
            ?maxSubmissionsPerPartition = maxSubmissionsPerPartition,
            ?pumpInterval = pumpInterval,
            ?logExternalState = logExternalState,
            ?idleDelay = idleDelay,
            ?maximizeOffsetWriting = maximizeOffsetWriting)

In a sense – when moving from Stateless Apps to Stateful Apps, we’re trading DB scaling complications (which are typical for Stateless Apps) for App scaling complications (typical for Stateful Apps). From my experience, such a trade-off is well-worth it.