Protocol Bindings
Configure protocol-specific bindings at server, channel, operation, and message levels. Detailed configuration for Kafka, AMQP, MQTT, WebSocket, and cloud messaging protocols.
Protocol bindings capture configuration that is specific to a particular messaging protocol. NeoArc supports bindings at four levels: server, channel, operation, and message. Each protocol defines different properties at each level.
Binding Levels
Server Bindings
Broker-wide settings: Schema Registry, client configuration, session parameters, and connection tuning.
Channel Bindings
Topic/queue configuration: partitions, replicas, retention policies, exchange types, and persistence settings.
Operation Bindings
Producer/consumer settings: consumer groups, client IDs, QoS levels, delivery modes, and acknowledgement policies.
Message Bindings
Message-level settings: key schemas, encoding, content types, and schema lookup strategies.
Apache Kafka
Kafka bindings are the most detailed, covering Schema Registry integration, topic management, consumer groups, and schema serialisation strategies.
AMQP 0-9-1
AMQP bindings cover exchange and queue configuration, message delivery modes, and routing.
MQTT / MQTT 5.0
MQTT bindings cover Quality of Service levels, session management, and last will configuration.
| Level | Key Properties |
|---|---|
| Server | Client ID, clean session, keep alive, session expiry, max packet size, last will (topic, QoS, message, retain) |
| Operation | QoS (0: at most once, 1: at least once, 2: exactly once), retain flag, message expiry interval |
| Message | Payload format indicator, content type, response topic |
Cloud Protocols
| Protocol | Channel Bindings |
|---|---|
| Amazon SNS | Topic name, IAM policy (JSON) |
| Amazon SQS | Queue name, FIFO queue, deduplication scope, delivery delay, visibility timeout, message retention |
| Google Pub/Sub | Topic, message retention duration, storage policy (allowed regions), schema settings (encoding, name) |
Enterprise Protocols
| Protocol | Key Bindings |
|---|---|
| IBM MQ | Server: group ID, queue manager, cipher spec, heartbeat. Channel: destination type (topic/queue), object name, partitioned, exclusive. Topic: durability, last message retained. |
| Solace PubSub+ | Server: message VPN, client name. Operation: destinations with delivery mode, queue config, topic subscriptions. |
| Apache Pulsar | Server: tenant, namespace. Channel: persistence mode, compaction, retention (time/size), TTL, deduplication. |