2017-07-20 19:42:32 -07:00
# Publish Subscribe
2019-08-19 17:06:08 +02:00
Publish Subscribe is also included on the stack. Currently, we have two PubSub implementation available [libp2p-floodsub ](https://github.com/libp2p/js-libp2p-floodsub ) and [libp2p-gossipsub ](https://github.com/ChainSafe/gossipsub-js ), with many more being researched at [research-pubsub ](https://github.com/libp2p/research-pubsub ).
2017-07-20 19:42:32 -07:00
We've seen many interesting use cases appear with this, here are some highlights:
- [Collaborative Text Editing ](https://www.youtube.com/watch?v=-kdx8rJd8rQ )
- [IPFS PubSub (using libp2p-floodsub) for IoT ](https://www.youtube.com/watch?v=qLpM5pBDGiE ).
- [Real Time distributed Applications ](https://www.youtube.com/watch?v=vQrbxyDPSXg )
## 1. Setting up a simple PubSub network on top of libp2p
2018-02-15 19:49:41 +01:00
For this example, we will use MulticastDNS for automatic Peer Discovery. This example is based the previous examples found in [Discovery Mechanisms ](../discovery-mechanisms ). You can find the complete version at [1.js ](./1.js ).
2017-07-20 19:42:32 -07:00
2019-08-19 17:06:08 +02:00
Using PubSub is super simple, you only need to provide the implementation of your choice and you are ready to go. No need for extra configuration.
2017-07-20 19:42:32 -07:00
```JavaScript
2019-04-11 15:52:04 +02:00
node1.once('peer:connect', (peer) => {
console.log('connected to %s', peer.id.toB58String())
2017-07-20 19:42:32 -07:00
2019-08-19 17:06:08 +02:00
series([
// node1 subscribes to "news"
(cb) => node1.pubsub.subscribe(
'news',
(msg) => console.log(`node1 received: ${msg.data.toString()}` ),
cb
),
(cb) => setTimeout(cb, 500),
// node2 subscribes to "news"
(cb) => node2.pubsub.subscribe(
'news',
(msg) => console.log(`node2 received: ${msg.data.toString()}` ),
cb
),
(cb) => setTimeout(cb, 500),
// node2 publishes "news" every second
(cb) => {
2018-02-22 07:06:21 +00:00
setInterval(() => {
node2.pubsub.publish(
'news',
Buffer.from('Bird bird bird, bird is the word!'),
2019-08-19 17:06:08 +02:00
(err) => {
if (err) { throw err }
}
2018-02-22 07:06:21 +00:00
)
}, 1000)
2019-08-19 17:06:08 +02:00
cb()
},
], (err) => {
if (err) { throw err }
})
2017-07-20 19:42:32 -07:00
})
```
The output of the program should look like:
```
> node 1.js
2019-04-11 15:52:04 +02:00
connected to QmWpvkKm6qHLhoxpWrTswY6UMNWDyn8hN265Qp9ZYvgS82
2019-08-19 17:06:08 +02:00
node2 received: Bird bird bird, bird is the word!
node1 received: Bird bird bird, bird is the word!
node2 received: Bird bird bird, bird is the word!
node1 received: Bird bird bird, bird is the word!
```
You can change the pubsub `emitSelf` option if you don't want the publishing node to receive its own messages.
```JavaScript
const defaults = {
config: {
peerDiscovery: {
mdns: {
interval: 2000,
enabled: true
}
},
pubsub: {
enabled: true,
emitSelf: false
}
}
}
2017-07-20 19:42:32 -07:00
```
## 2. Future work
libp2p/IPFS PubSub is enabling a whole set of Distributed Real Time applications using CRDT (Conflict-Free Replicated Data Types). It is still going through heavy research (and hacking) and we invite you to join the conversation at [research-CRDT ](https://github.com/ipfs/research-CRDT ). Here is a list of some of the exciting examples:
- [PubSub Room ](https://github.com/ipfs-labs/ipfs-pubsub-room )
- [Live DB - A always in Sync DB using CRDT ](https://github.com/ipfs-labs/ipfs-live-db )
- [IIIF Annotations over IPFS, CRDT and libp2p ](https://www.youtube.com/watch?v=hmAniA6g9D0&feature=youtu.be&t=10m40s )
- [orbit.chat - p2p chat application, fully running in the browser with js-ipfs, js-libp2p and orbit-db ](http://orbit.chat/ )