Skip to main content

  • Core Products

  • Add-Ons

  • Extensions Marketplace

Chat and Signaling comparison

The choice between Chat and Signaling requires a comprehensive evaluation according to your business demands and subsequent extensions.

The main use cases for Signaling and Chat are:

  • Chat targets instant messaging scenario, it provides mature SDK integration and versatile user experience.
  • Signaling is widely used in multiple scenarios.

The following table explains the similarities and differences between Signaling and Chat:

DomainSignalingChat
Technical architectureA distributed system where data can be processed and switched on edge nodes.A centralized system where data is processed and switched on the central node.
Product positioningA highly reliable synchronization and transportation service for signals, messages, and statuses that features low latency and high concurrency.A highly interactive instant messaging service that provides contact management, multimedia messages, chat rooms, chat groups, data storage, and content moderation.
Latency performanceUltra-low latency: < 100 ms.Low latency: 200 ms to 400 ms.
Applicable scenarios
  • Online education with collaborative operations of teacher and students on slides and other elements
  • Real-time data synchronization of the statuses, positions, and attributes from players.
  • Virtual gifting for live streamers.
  • Data reporting by IoT sensors.
  • Call invitations and host management in voice calls and video calls.
  • Instant messaging for business.
  • Group chats in games.
  • Interactive chats in live streaming channels.

Chat and Signaling functionalities overlap in certain scenarios, such as bullet screen.

vundefined