fsprojects/pulsar-client-dotnet
55.9
Adequate · 13 November 2026
15.8k
lines of production code
F#
primary language
4
measurements over time
What this system is
Features
Added F\# example demonstrating JSON schema usage
A new F\# example file (Schema.fs) has been added to the FsharpExamples directory. This example demonstrates how to configure a Pulsar producer and consumer with a JSON schema for a Product type, including sending and receiving messages with schema validation.
FsharpExamples · high confidence
Initial C\# example suite with authentication, schema, and telemetry demos
The C\# examples project now includes a comprehensive set of runnable demonstrations for the Pulsar client. Users can explore basic messaging (Simple.cs), custom message properties (CustomProps.cs), and a realistic production pattern with logging and cancellation (RealWorld.cs). The suite also covers advanced capabilities: schema-validated JSON serialization (Schema.cs), transactional messaging across topics (Transaction.cs), OpenTelemetry tracing via interceptors (Telemetry.cs), TLS mutual authentication (TlsAuthentication.cs), and OAuth2 client-credentials authentication (Oauth2.cs). A new entry point (Program.cs) allows toggling these examples, and a runtime config template (runtimeconfig.template.json) optimizes GC settings for performance.
examples/CsharpExamples · high confidence
Initial release of the Pulsar .NET client API surface
This change introduces the complete public API for the Pulsar .NET client library, defining the core interfaces and configuration models for interacting with Apache Pulsar. It establishes the foundational types for producers (IProducer), consumers (IConsumer), and readers (IReader), along with their respective builders (ConsumerBuilder, ProducerBuilder) and configuration records (ConsumerConfiguration, ProducerConfiguration). The diff adds support for advanced messaging features including dead-letter processing (DeadLetterPolicy, IDeadLetterProcessor), message encryption and decryption (IMessageEncryptor, IMessageDecryptor), schema handling (ISchema), and interceptors (IConsumerInterceptor, IProducerInterceptor). It also introduces authentication mechanisms (Authentication, AuthenticationFactory, AuthenticationFactoryOAuth2) and cluster failover strategies (AutoClusterFailover, ControlledClusterFailover) to ensure robust connectivity and reliability.
src/Pulsar.Client/Api · high confidence
Introduce transaction support with coordinator and builder components
Added new \TransactionBuilder\ and \TransactionCoordinatorClient\ modules to enable transactional operations. The \TransactionBuilder\ provides a fluent API for configuring transaction timeouts and building transactions, while the \TransactionCoordinatorClient\ manages the lifecycle of the transaction coordinator, including connecting to metadata partitions, handling start/close states, and routing operations like adding publish partitions, subscriptions, committing, and aborting transactions to the appropriate handlers.
src/Pulsar.Client/Transaction · high confidence
Introduces core client infrastructure and data models
This change adds the foundational Common module for the Pulsar .NET client, establishing the internal data structures and utilities required for client operation. It defines typed identifiers (LedgerId, EntryId, ProducerId, etc.) using F\# measures to prevent type confusion, and introduces the Message and Messages types to handle payload data, keys, properties, and schema information. It also implements TopicName and NamespaceName parsers to validate and normalize topic addresses, and provides serialization logic in Commands.fs for constructing protocol buffers (including support for chunked messages and transactions). Additionally, it adds a configurable logging wrapper and utility functions for stream management and asynchronous task handling.
src/Pulsar.Client/Common · high confidence
Introduction of comprehensive schema serialization support
The Pulsar client now includes a full suite of schema implementations in the \src/Pulsar.Client/Schema\ directory, enabling structured data handling for Pulsar topics. This update adds support for primitive types (Boolean, Byte, Int, Long, Short, Float, Double, String, Bytes, Date, Time, Timestamp), complex formats (Avro, JSON, Protobuf, Protobuf Native), and composite structures (KeyValue). It also introduces auto-consume and auto-produce schema stubs for flexible schema negotiation, along with a multi-version schema info provider to handle schema evolution and caching.
src/Pulsar.Client/Schema · high confidence
New F\# client examples and runtime configuration
The examples/FsharpExamples directory now includes a comprehensive set of F\# demonstration projects covering core messaging, advanced features, and security. Users can explore basic producer/consumer patterns (Simple.fs), custom message properties (CustomProps.fs), schema-based serialization with JSON (Schema.fs), and transactional messaging across topics (Transaction.fs). Additional examples demonstrate the Reader API for scanning topics (Reader.fs), robust error handling and cancellation in real-world scenarios (RealWorld.fs), and OpenTelemetry integration for distributed tracing (Telemetry.fs). Security features are illustrated through TLS authentication (TlsAuthentication.fs) and OAuth2 client credentials flow (Oauth2.fs). A runtimeconfig.template.json is also added to configure the .NET runtime for server GC and heap settings.
examples/FsharpExamples · high confidence
New internal infrastructure for acknowledgments, chunked messages, and connection handling
This change introduces several new internal components to the Pulsar client to support advanced message handling and connectivity. The AcknowledgmentsGroupingTracker manages the batching and flushing of individual, cumulative, and batch-index acknowledgments to the broker. The ChunkedMessageTracker handles the assembly, decompression, and lifecycle management of large messages split into chunks, including expiration logic for incomplete messages. A new Backoff module provides configurable exponential backoff with mandatory stop times for retry operations. Additionally, the BinaryLookupService implements topic metadata and broker lookup logic with retry support, while the ConnectionPool manages socket connections, including dual-mode IPv6 support and TLS configuration. These components collectively enable features like chunked message consumption, efficient acknowledgment grouping, and robust connection management.
src/Pulsar.Client/Internal · high confidence
OAuth2 authentication support with data URI credentials
The Pulsar client now supports OAuth2 authentication, allowing users to authenticate with Pulsar brokers using an issuer URL, audience, and credentials. A key addition is the ability to provide credentials via a \data:application/json;base64\ URI, enabling secure credential injection without requiring a file system path. The implementation handles token fetching, caching, and automatic refresh before expiry, with concurrent refresh requests shared to avoid redundant network calls.
Pulsar.Client · high confidence
OpenTelemetry tracing for Pulsar producer and consumer interceptors
Added OpenTelemetry integration for Pulsar messaging via new \OTelProducerInterceptor\ and \OtelConsumerInterceptor\ components. The producer interceptor now creates trace activities for message sends, injecting trace context into message properties for distributed tracing and caching activities to record success or error status upon acknowledgement. The consumer interceptor extracts upstream trace context from incoming messages, creates receive activities, and manages activity lifecycles (including cumulative acknowledgements, timeouts, and negative acknowledgements) through a background task processing a command channel, ensuring proper span closure and error tagging.
src/Pulsar.Client.Otel · high confidence
Architecture
Repository restructured with .NET 10 SDK and new support packages
The project has been reorganized into a new solution structure featuring the main \Pulsar.Client\ library alongside new support packages \Pulsar.Client.Proto\ (for C\# protocol buffer support) and \Pulsar.Client.Otel\ (for OpenTelemetry integration). The repository now targets .NET 8 for the main library but requires the .NET 10 SDK for building, as enforced by the new \global.json\. This change also introduces a comprehensive architecture document, updated CI workflows, and a detailed contributing guide.
(repo-wide) · high confidence
Behavioural changes
New RSA-based message encryption and decryption implementation
The Pulsar client now uses a new cryptographic implementation in \MessageCrypto.fs\ that encrypts messages using AES-256-GCM and secures the symmetric key with RSA-OAEP-SHA1. This change introduces \MessageEncryptor\ and \MessageDecryptor\ classes that handle key loading via \ICryptoKeyReader\, cache decrypted symmetric keys in memory for performance, and support key rotation through \UpdateEncryptionKeys\.
src/Pulsar.Client/Crypto · high confidence
Updated Pulsar protocol definitions and added CRC32C and MurmurHash3 utilities
The Pulsar.Client.Proto library has been updated with new protocol buffer definitions (PulsarApi.proto) and their corresponding C\# generated code (Generated.cs), reflecting changes in the Pulsar message format such as transaction support and chunked messages. Additionally, the project now includes a new CRC32C implementation (Crc32c.cs) using .NET intrinsics for performance, a MurmurHash3 utility (MurmurHash3.cs) for partitioning, and a DynamicJsonConverter for handling JSON schema data.
src/Pulsar.Client.Proto · high confidence
Test coverage
Added Avro code generation and integration tests for Pulsar client; Internal visibility configuration for test assemblies.
Dependencies
Upgrade to .NET 10 and update core dependencies
The project has been upgraded to target .NET 10 (net10.0) for example and test projects, while the core libraries (Pulsar.Client, Pulsar.Client.Otel, Pulsar.Client.Proto) target .NET 8. This change includes updating the main client library to version 3.19.3 and the OpenTelemetry plugin to 1.1.0. Key dependency updates include Microsoft.Extensions.Logging and related packages to version 10.0.x, OpenTelemetry packages to 1.15.3, and protobuf-net to 3.2.30. The examples now reference Pulsar.Client 3.16.0, reflecting the current stable release for consumers.
(dependencies) · high confidence
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
Score
- CAI 54 → 56 (+1.9)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.3) — scores are not directly comparable.
Lenses
- Code Health 65 → 61 (-3.5)
- Architecture 96 → 96 (-0.1)
- Maturity 61 → 62 (+0.7)
- Readiness 38 → 43 (+5.2)
- Security 79 → 78 (-1.0)
- Performance 85 → 85 (+0.0)
Resolved (36)
- Change coupling: ProducerBuilder.fs ↔ ProducerImpl.fs (src/Pulsar.Client/Api/ProducerBuilder.fs)
- Change coupling: ProducerImpl.fs ↔ TransactionMetaStoreHandler.fs (src/Pulsar.Client/Internal/ProducerImpl.fs)
- Coverage not measured — no coverage collector is wired up
- Duplicated block (10 lines × 3) (src/Pulsar.Client/Internal/TransactionMetaStoreHandler.fs)
- Duplicated block (10 lines × 3) (src/Pulsar.Client/Internal/TransactionMetaStoreHandler.fs)
- Duplicated block (17 lines × 2) (src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs)
- Duplicated block (19 lines × 2) (src/Pulsar.Client/Internal/ConsumerImpl.fs)
- Duplicated block (6 lines × 2) (src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs)
- Duplicated block (6 lines × 3) (src/Pulsar.Client/Internal/ConsumerImpl.fs)
- Duplicated block (7 lines × 2) (src/Pulsar.Client/Internal/ProducerImpl.fs)
- Duplicated block (8 lines × 2) (src/Pulsar.Client/Internal/MultiTopicsReaderImpl.fs)
- Duplicated block (9 lines × 2) (src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs)
- Duplicated block (9 lines × 2) (src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs)
- Duplicated block (9–10 lines × 2) (src/Pulsar.Client/Internal/AcknowledgmentsGroupingTracker.fs)
- Duplicated block (9–10 lines × 2) (src/Pulsar.Client/Internal/NegativeAcksTracker.fs)
- Flaky test: UnitTests::Stats.Stats.Consumer stats
- IL efficiency: 9 authored method(s) exceed the IL budget (src/Pulsar.Client/Internal/ConsumerImpl.fs)
- Inconsistent casing in method names following the 'Reset' verb. Most methods use PascalCase for the property name being reset (e.g., ResetMaxMessageSize, ResetNumMessages), but these two use camelCase for the suffix.
- Leaked secret: high-entropy-secret (examples/Oauth2Files/credentials_file.json)
- Leaked secret: signing-key (examples/Oauth2Files/credentials_file.json)
- …and 16 more
New (28)
- Change coupling: MultiTopicsConsumerImpl.fs ↔ ReaderImpl.fs (src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs)
- Change-coupling hub: ProducerImpl.fs → ProducerBuilder.fs, ReaderImpl.fs, TransactionMetaStoreHandler.fs (src/Pulsar.Client/Internal/ProducerImpl.fs)
- Duplicated block (10 lines × 3) (src/Pulsar.Client/Internal/TransactionMetaStoreHandler.fs)
- Duplicated block (12 lines × 2) (src/Pulsar.Client/Internal/MultiTopicsConsumerImpl.fs)
- Duplicated block (6 lines × 2) (src/Pulsar.Client/Internal/NegativeAcksTracker.fs)
- Duplicated block (7 lines × 2) (src/Pulsar.Client/Internal/ConsumerImpl.fs)
- Duplicated block (9 lines × 3) (src/Pulsar.Client/Internal/TransactionMetaStoreHandler.fs)
- Edited copies of one member (3 members, 17+ corresponding lines) (src/Pulsar.Client/Schema/DateSchema.fs)
- Edited copies of one member (7 members, 15+ corresponding lines) (src/Pulsar.Client/Schema/BooleanSchema.fs)
- Edited copy of a member (10 corresponding lines) (src/Pulsar.Client/Schema/AutoConsumeSchema.fs)
- Edited copy of a member (30 corresponding lines) (examples/CsharpExamples/Oauth2.cs)
- Edited copy of a member (42 corresponding lines) (examples/FsharpExamples/Simple.fs)
- Edited copy of a member (71 corresponding lines) (src/Pulsar.Client.Proto/MurmurHash3.cs)
- Edited copy of a member (97 corresponding lines) (src/Pulsar.Client/Internal/MultiTopicsReaderImpl.fs)
- Members sharing a duplicated core (4 members, 50+ identical tokens) (src/Pulsar.Client/Internal/ConsumerStatsImpl.fs)
- Off-boarding risk: anonymized user #1
- Orphaned file (src/Pulsar.Client.Otel/OtelConsumerInterceptor.fs)
- Orphaned file (src/Pulsar.Client/Common/ServiceUri.fs)
- Orphaned file (src/Pulsar.Client/Internal/ConsumerStatsImpl.fs)
- Orphaned file (src/Pulsar.Client/Internal/ProducerStatsImpl.fs)
- …and 8 more
Changes since last survey
- 12 commits — 11 feature/other, 1 fixes
By area
- src/Pulsar.Client — 9 commits
- tests/UnitTests — 2 commits
- tests/IntegrationTests — 1 commit
Notable commits
- fix: Batch receive stall fixes (#382)
- change: Answer requests left in ClientCnx mailboxes after the connection is deactivated (#388)
- change: Bumped version
- change: Bumped version
- change: Bumped version
- change: Handle stopped children and deleted topics as the Java client does (#385)
- change: Keep multi-topic consumers running when a child consumer stops (#384)
- change: Keep requests from waiting on loops and connections that can't answer (#394)
- change: Read a frame as soon as its last bytes arrive on TLS connections (#393)
- change: Recover consumers and producers from unexpected failures (#392)
- change: Retry errors during creation as the Java client does (#386)
- change: Subscribe partition consumers under the parent consumer's name (#389)
Architecture
- Unchanged — 0 containers · 2 contexts · 1 edges
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
fsprojects/pulsar-client-dotnet was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.
About this page
- The score is its most recent published measurement, taken on 13 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 477793f96b60bec6bc03a8d1c9e2c0ab70b1ae90 — the exact code this score is about.
- Scored under rubric-2026.11.3 — the same rubric and the same method as every other entry in this index.
- Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.61+preprod-b8b1a43ae4c3.