Channel Basics

A channel is a fundamental communication pathway that facilitates the passing of data between devices within the PubNub service.

Channels are hosted on PubNub servers, and you interact with them using PubNub SDKs or directly via the REST API.

This pub/sub model allows for seamless and efficient asynchronous processing of messages, supporting both real-time updates and independent operation of different components within your application. For instance, in a real-time chat application, the messaging, notification, and analytics components can function independently and communicate through channels, enforcing modularity and scalability.

We are fast

Any device listening to a channel receives all messages in about 30ms regardless of their physical location in the world, ensuring swift communication across the globe.

Channel creation​

You don't have to explicitly define or create channels on the server in advance. The channel is automatically created when you publish a message to a particular channel for the first time.

Channel entity​

PubNub SDKs use local representations of channels called Channel entities

Entity

A subscribable object within a PubNub SDK that allows you to perform context-specific operations.
to facilitate working with channels. This class of objects abstracts the complexities of channel management, enabling better design patterns, such as decoupling different parts of your application for more modular and maintainable code.

For more information, refer to Entities.

Channel limits​

There is no limit to the number of channels or the number of users in a channel you can have. A device can listen to thousands of channels simultaneously through a single open connection, making PubNub ideal for scalable group communication.

Channel types​

Channels can represent any place where messages are sent and received, supporting various communication models like direct channels for one-to-one private messaging or group channels for many-to-many interaction scenarios. Broadcast and unicast channels provide additional flexibility for specific use cases.

Here are some useful channel configurations:

Direct channels for one-to-one in-app messaging between two users. You can make these channels private to keep the messages secure between the users.

const PubNub = require('pubnub');

// Initialize the PubNub client with your publish and subscribe keys
const pubnub = new PubNub({
  publishKey: 'yourPublishKey',
  subscribeKey: 'yourSubscribeKey',
  userId: 'user1-unique-id', // Use unique user IDs for authentication
  authKey: 'user1AuthKey',   // Use an authentication key for security
  ssl: true                  // Enable SSL for secure communication
});

// Define the direct channel for one-to-one messaging between two specific users
const directChannel = 'direct.user1.user2'; // Example channel name

// Subscribe to the direct channel
show all 48 lines

Group channels serve as a collective category for many-to-many in-app messaging among multiple users, forming a community communication system, such as a chat room for friends or family.

const PubNub = require('pubnub');

// Initialize the PubNub client with your publish and subscribe keys
const pubnub = new PubNub({
  publishKey: 'yourPublishKey',
  subscribeKey: 'yourSubscribeKey',
  userId: 'user1-unique-id', // Use unique user IDs for authentication
  authKey: 'user1AuthKey',   // Use an authentication key for security if necessary
  ssl: true                  // Enable SSL for secure communication
});

// Define the group channel for in-app messaging
const groupChannel = 'group.family'; // Example channel name for a family group

// Subscribe to the group channel
show all 68 lines

Broadcast channels for announcements, polls, and other situations in which you want to broadcast messages in a one-to-many arrangement.

const PubNub = require('pubnub');

// Initialize the PubNub client with your publish and subscribe keys
const pubnub = new PubNub({
  publishKey: 'yourPublishKey',
  subscribeKey: 'yourSubscribeKey',
  userId: 'broadcaster-unique-id', // Use a unique ID for the broadcaster
  ssl: true                        // Enable SSL for secure communication
});

// Define the broadcast channel for one-to-many communication
const broadcastChannel = 'broadcast.announcements'; // Example channel for announcements

// Subscribe to the broadcast channel
const channel = pubnub.channel(broadcastChannel);
show all 51 lines

Unicast channels for poll responses, sensor inputs, location data, and other situations in which you want to aggregate messages in a many-to-one arrangement.

const PubNub = require('pubnub');

// Initialize the PubNub client with your publish and subscribe keys
const pubnub = new PubNub({
  publishKey: 'yourPublishKey',
  subscribeKey: 'yourSubscribeKey',
  userId: 'listener-unique-id', // Unique ID for the device/server listening for inputs
  ssl: true                      // Enable SSL for secure communication
});

// Define the unicast channel for aggregating messages
const unicastChannel = 'unicast.dataCollector'; // Example channel for aggregating data

// Subscribe to the unicast channel
const channel = pubnub.channel(unicastChannel);
show all 60 lines

Channel groups allow you to bundle thousands of channels into a group that can be identified by name. When you subscribe to a channel group, you receive data from all the channels the channel group contains.

Channel names​

A channel name can be any alphanumeric string up to 92 UTF-8 characters. Channel names are unique per PubNub key set, and you can have the same name in another key, even within the same PubNub account. In other words, a PubNub key set is a namespace for your channels.

Invalid characters​

, : * / \ and Unicode Zero, whitespace, and non-printable ASCII characters.

Valid characters​

_ - = @ . ! $ # % & ^ ;

A period (.) is valid, however it's a special character that's used for wildcard features and is encouraged to be used strategically to leverage wildcard channel subscribe and Function wildcard channel binding.

Channel name validator​

Check if your channel name is valid using our channel name validator.

Naming conventions​

When it comes to naming your channels, we recommend that you provide a prefix that identifies the purpose of the channel or the types of messages that will be sent over those types of channels.

Following that prefix with a . character further enhances the usefulness of the channel name concerning the wildcard features with several PubNub features, like wildcard subscribe, wildcard channel function binding, and advanced Presence configuration.

For further details on channel naming recommendations, refer to Channel Naming Conventions.

Securing channels​

You can secure your channels by controlling the access to them using PubNub's Access Manager.

With Access Manager disabled, any client can send and receive messages on any channel. This is fine while you're learning to use PubNub but eventually, you'll need to secure your channels.

For comprehensive protection across your app, refer to our documentation on Access Control in the Security section.

Last updated on
On this page