Ross ROSS = Recommend OSS · open-source software intelligence for agents

eclipse-ecal/ecal

📦 eCAL - enhanced Communication Abstraction Layer. A high performance publish-subscribe, client-server cross-plattform middleware. observed · 2026-08-28

github.com/eclipse-ecal/ecal · homepage · C++ · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

87/100

  • Activity 98
  • Release rhythm 65
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.

  • gap_med: 36
  • age_days: 2648
  • days_rel: 153
  • days_push: 14
  • n_releases_24m: 8

Full methodology

Adoption not part of the score

1045 stars · 219 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

eCAL is a high-performance, brokerless middleware for interprocess communication on a single machine or across a network, offering publish-subscribe and client-server patterns with automatic transport selection (shared memory, UDP, TCP). It includes tooling for recording, replay, and monitoring of data flows, with C++/C APIs and bindings for Python, C#, and Rust.

Use cases

  • send high-throughput sensor data between processes on one machine
  • build pub/sub communication between nodes in a robot or vehicle network
  • record and replay message streams for autonomous driving development
  • replace ROS2 or ZeroMQ with a zero-configuration IPC middleware
  • connect C++ and Python components over shared memory
  • monitor live data flows across a distributed system

When to choose

  • you need very fast local IPC (GB/s) with shared memory transport
  • you want brokerless pub/sub with near-zero configuration
  • you work in robotics, autonomous driving, or simulation (Matlab Simulink, ROS2 integration)
  • you need decentralized recording, replay, and monitoring tooling built in

When to avoid

  • you need broker-based messaging with persistent queues or guaranteed delivery
  • you only need simple REST or HTTP APIs between services
  • your stack is JVM or .NET only without C++/Python integration
  • you need a lightweight single-language library rather than a full middleware ecosystem

Facets

library · maturity active

message-queue serialization rpc middleware microservices autonomous-vehicles robotics cpp python cross-platform windows publish-subscribe interprocess-communication shared-memory brokerless client-server protobuf data-recording hdf5 ros2 real-time linux macos

2 sources

Member repositories

RepositoryRoleHealth v2
eclipse-ecal/ecalmain87

For agents

markdown · JSON · MCP: product_card(name="eclipse-ecal/ecal")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem