Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ADR-23 JetStream Simplified API #125

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
37 changes: 37 additions & 0 deletions adr/ADR-23.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,37 @@
# JetStream Simplified Client API

|Metadata| Value |
|--------|-------------------|
|Date | 2022-06-27 |
|Author | @aricart, @tbeets |
|Status | Proposed |
|Tags | jetstream, client |

## Context and Problem Statement

JetStream implements signaling choreography between client and server to affect the lifecycle
of streams and stream consumers and implement At-Least-Once message publishing and delivery end-to-end.

An app developer could implement and use JetStream leveraging only NATS pub-sub "core" primitives, but this would not be
productive for typical application development, thus NATS client libraries have been enhanced with JetStream
methods and abstractive helper features.

With community uptake and learnings, it's clear that first-generation client library abstractions are of the "leaky" variety, requiring the app developer to
have both intimate knowledge of low-level JetStream architecture and choreography semantics on the one hand **and** obscuring some
runtime actions in others, often causing developer confusion and misunderstanding.

## [Context | References | Prior Work]

[What does the reader need to know before the design. These sections and optional, can be separate or combined.]

## Design

[If this is a specification or actual design, write something here.]

## Decision

[Maybe this was just an architectural decision...]

## Consequences

[Any consequences of this design, such as breaking change or Vorpal Bunnies]