NNovaNetworkClientSwift networkingGitHub ↗

Architecture

Core concepts

A mental model for predictable networking under concurrency and failure.

01

Request identity

Method, canonical URL, selected headers, body, and authScope form the fingerprint used to decide whether work is equivalent.

02

Shared ownership

Callers await one underlying task but retain independent cancellation ownership. The network operation ends when no interested caller remains.

03

Freshness vs overlap

Coalescing shares work that overlaps in time. Caching can serve a later caller according to an explicit freshness policy.

04

Bounded resilience

Retry, auth refresh, batch concurrency, reconnect, and replay all need finite limits that match the product’s failure contract.

05

Typed boundaries

APIRequest describes wire intent. Endpoint adds a reusable typed response contract. NetworkClient owns execution policies.

06

Operational visibility

Lifecycle events and telemetry hooks expose coalescing, retries, queues, batches, and realtime transitions without changing feature code.

Ready to ship?

Turn the concepts into a production configuration.

Add bounded resilience