Skip to content

Messaging (Pub-Sub)

In the world of serverless and edge-native computing, efficient communication between services is crucial. Taubyte’s messaging resource, built on the publisher-subscriber model, provides a robust and scalable solution to meet this need. This communication paradigm is excellent for creating distributed systems where components can interact without knowledge of each other.


The messaging resources are genuinely serverless. This means there is no pre-set broker requiring ongoing management. Instead, brokers are provisioned dynamically when necessary, reducing complexity and allowing developers to focus on their application’s logic.

Message Propagation through Gossip

In Taubyte’s pub-sub system, messages propagate using a gossip protocol. This reliable and efficient approach to information distribution ensures swift and accurate message delivery to all nodes in the network, even in systems with many nodes.

Message Signing

Every message in Taubyte’s messaging system is signed to ensure message integrity and authenticity. This added layer of security helps safeguard against unauthorized or malicious messages.

Dfunction Triggering

An innovative feature of Taubyte’s messaging system is its ability to trigger dfunctions. This means that the receipt of a pub-sub message can act as an event that initiates the execution of a specific dfunction, enabling event-driven architectures.

Configuration Flexibility

The messaging system can be tailored to meet the specific needs of your application. This includes settings such as whether the messaging system should be local or global, the matching pattern for channels, and the selection of bridges to connect with external systems.

Here’s an example of a messaging configuration:

id: QmSwQn9EqEagC46yDBFxAxZN9oTi8dabaAhhKeLmTvTiU9
description:  Minting PubSub
tags: []
local: false
    regex: false
    match: nftMinted
        enable: false
        enable: false

Here’s what each component of the configuration means:

  • id: The unique identifier for the messaging resource.
  • local: This flag indicates whether the messaging resource is local to the node or not. If set to false, messages will propagate through the network.
  • channel: This section defines the channel configuration.
    • match: The matching pattern for the channel.
  • bridges: This section specifies the bridges to connect the Taubyte messaging system with external systems.
    • websocket: The configuration for the WebSocket bridge.

With its flexibility, security, and efficiency, the Taubyte messaging system forms a cornerstone of complex distributed systems built using the Taubyte edge-native computing platform.