About JetStream

    • The system must be easy to configure and operate and be observable.
    • The system must be secure and operate well with NATS 2.0 security models.
    • The system must scale horizontally and be applicable to a high ingestion rate.
    • The system must self heal and always be available.
    • The system must have an API that is closer to core NATS.
    • The system must allow NATS messages to be part of a stream as desired.
    • The system must display payload agnostic behavior.
    • The system must not have third party dependencies.
    • At-least-once delivery; exactly once within a window
    • Wildcard support
    • Account aware
    • Data at rest encryption
    • Cleanse specific messages (GDPR)
    • Horizontal scalability
    • Persist Streams and replay via Consumers