Official ADM libraries that connect an ADM program to
infrastructure services. Each is written in ADM over std.net, published as
adm.network.<name> and signed by the admlang publisher. They live outside the standard
library so that a fix or a new protocol version ships without a std release.
| Library | Service | How it connects |
|---|---|---|
adm.network.redis |
Redis, Valkey and servers that speak RESP | RESP2 and RESP3 over TCP, TLS or a Unix socket; Redis Cluster and Sentinel |
adm.network.amqp |
RabbitMQ and brokers that speak AMQP 0-9-1 | AMQP 0-9-1 over TCP or TLS: exchanges, queues, confirms, consumers, transactions |
adm.network.kafka |
Apache Kafka 2.4 and later, and services that speak its protocol (Redpanda, MSK, Event Hubs) | The Kafka protocol over TCP or TLS: producer, consumer groups, transactions, topic administration |
adm.network.s3 |
Amazon S3 and servers that speak its API (MinIO, Ceph, Garage, R2, B2) | Signature Version 4 over HTTP or HTTPS, path or virtual-host addressing |
adm.network.memcached |
memcached 1.6 and later, ElastiCache, Memorystore | the text and meta protocols over TCP, Unix sockets or TLS; consistent hashing over several servers |
adm.network.etcd |
etcd 3.4 and later | the v3 gRPC API over TLS: key-value and transactions, watches, leases, locks and elections |
The suites that need a server pass without running unless they are told where one is:
ADM_TEST_REDIS=127.0.0.1:6379 adm test network/redis
ADM_TEST_S3=http://key:secret@127.0.0.1:9000 adm test network/s3
ADM_TEST_AMQP=guest:guest@127.0.0.1:5672 adm test network/amqp
ADM_TEST_KAFKA=127.0.0.1:9092 adm test network/kafka
ADM_TEST_MEMCACHED=127.0.0.1:11211 adm test network/memcached
ADM_TEST_ETCD=127.0.0.1:2379 adm test network/etcdEach library's README says what the server must hold.