Skip to content

No formal mechanism for limiting reducer state size #12

@randysecrist

Description

@randysecrist

Reducers are able to store whatever they want in state without limits. This puts difficult to pinpoint pressure on the platform and produces bursty performance followed by bursty slow downs.

Perhap could lookup at the returning state and decide some default strategy for breaking state up. However the effectiveness of a such a default strategy being applicable to a wide range of specific data model and workloads is questionable.

An alternate strategy would be to decide which workloads perhap is to carry and let it emit events outside into Kafka or another system to allow other systems to process additional workloads.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions