Skip to content
CAI
Software that uses CAICheck a score

exponentially/extreme

61.4

Adequate · 9 November 2026

3k

lines of production code

Elixir

primary language

11

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

This system is an Elixir client library for EventStoreDB that facilitates interaction with the Event Store protocol via Protocol Buffers. It provides core capabilities for writing, deleting, and reading events from streams, as well as subscribing to event streams with support for backpressure and fanout patterns. The library also handles cluster-aware connections through gossip resolution and manages persistent subscriptions with server-side checkpointing and acknowledgment strategies.

Features

Automated regeneration of Elixir protobuf messages

A new shell script, scripts/gen\_messages.sh, has been added to automate the regeneration of the Elixir protobuf source file (lib/extreme/messages/event\_store.pb.ex) from the proto definition. This script handles necessary workarounds for protoc enum naming conflicts and ensures the generated code is formatted, streamlining the process of keeping message definitions in sync with the protocol buffer schema.

scripts · high confidence

Initial Event Store protocol definition

The \include/event\_store.proto\ file introduces the Protocol Buffers schema for the Event Store service. This definition establishes the core data structures and operations for event handling, including message types for writing events (\WriteEvents\), deleting streams (\DeleteStream\), and managing transactions (\TransactionStart\, \TransactionWrite\, \TransactionCommit\). It also defines the read operations, specifically supporting both forward and backward reading of stream events (\ReadStreamEvents\, \ReadStreamEventsBackward\) and reading all events (\ReadAllEvents\), along with their corresponding response structures and result enums.

include · high confidence

Introduce cluster-aware connection and persistent subscription support

The library now supports connecting to EventStore clusters by resolving the appropriate node via gossip protocol, configurable via new \:cluster\ and \:cluster\_dns\ connection types. It also adds a new persistent subscription API, allowing asynchronous event processing with server-side checkpointing, acknowledgments, and retry/park strategies. Additionally, the underlying protobuf message generation has been updated to use the \protobuf\ library (v0.17.1) instead of the deprecated \exprotobuf\.

lib/extreme · high confidence

New event subscription and processing listeners

The library introduces three new listener modules for consuming events from EventStore: \Extreme.Listener\ for standard stream subscription with batch reading, \Extreme.FanoutListener\ for live-only event streaming (similar to a fanout exchange), and \Extreme.ListenerWithBackPressure\ which uses an event producer to apply backpressure when the buffer reaches a configurable limit. These modules provide macros (\use Extreme.Listener\, etc.) to simplify implementation, offering features like automatic subscription management, pause/resume capabilities, and configurable options such as \read\_per\_page\, \ack\_timeout\, and \max\_buffered\.

lib · high confidence

Behavioural changes

Structured environment-based configuration for Extreme

The application now uses a standard Elixir configuration structure with a main config.exs that imports environment-specific files (dev.exs, prod.exs, test.exs). In development, console logging is set to debug level. In the test environment, the logger includes process metadata, ExUnit receive timeouts are increased to 10 seconds, and the Extreme client connection details (host, port, credentials) are configured, reading the host and port from environment variables EVENTSTORE\_HOST and EVENTSTORE\_PORT with sensible defaults.

config · high confidence

Upgrade to protobuf 0.17 and Elixir 1.16+ with breaking message changes

The library now requires Elixir 1.16 or later and replaces the exprotobuf dependency with protobuf 0.17.1. This upgrade introduces several breaking changes for users: unset events in resolved structures now decode as \nil\ instead of empty structs, string/bytes fields must be binaries, and message structs include new \\_\_unknown\fields\\\ and \\\protobuf\\_\ keys. Additionally, \exprotobuf\-specific functions like \encode\_delimited/1\ and \atom/1\ have been removed in favor of standard \encode/1\ and \key/1\. Encoding failures now return explicit error tuples instead of timing out or failing silently, and persistent subscription acknowledgments that fail to encode will stop the subscription. UUID generation has also switched to UUIDv7.

(repo-wide) · high confidence

Test coverage

Added test coverage for Extreme client components; Added test suite for listeners, subscriptions, and benchmarks; Added test support utilities for EventStoreDB integration testing.

Dependencies

Update project dependencies and Elixir version requirement

The Extreme library now requires Elixir \~\> 1.16 and updates its core dependencies: protobuf is set to \~\> 0.17.1, telemetry to \~\> 0.4 or \~\> 1.0, and jason (optional) to \~\> 1.1. Test dependencies exvcr and ex\_doc are also updated, with the lockfile reflecting specific versions like telemetry 1.3.0 and protobuf 0.17.1.

(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 62 → 61 (-0.9)
  • Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

Lenses

  • Code Health 98 → 98 (+0.0)
  • Architecture 99 → 99 (+0.0)
  • Maturity 49 → 49 (+0.0)
  • Readiness 58 → 58 (+0.0)
  • Security 84 → 77 (-6.6)

Resolved (1)

  • Off-boarding risk: anonymized user #1

New (1)

  • Off-boarding risk: anonymized user #1

Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

Survey your own repository

exponentially/extreme 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 9 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 f339a4b395c60a19b95a46f5c95838b8fe07111f — the exact code this score is about.
  • Scored under rubric-2026.11.2 — 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.3+preprod-bb0cb800cd0f.