Chat Services at 2.0

[chpapa]

Description

Chat is the MOST popular services in v1, after the launch of NEXT Chat is definitely the first services we will want to port to NEXT.

When we reimplement this, one should reference the v1 doc for the basic features, here are some extra features we were asked and should consider in design decision:

• Support translation of chat room messages Ref: #157
• Support Broadcast Channel (like Telegram announcement channel) Ref: #197
• Support offline message cache and sync Ref: #64
• User online indicator Ref: #65 ,p.s. there were some argument before weather it should be chat or auth gear's feature
• UIKit for Android, iOS, React Native, Web
• Push notification support (#123)
• Keywords / certain type of info suppression (#156)
• End to end encryption with libsignal

Some features unlikely to be implemented in short term but got asked by customers all the time:

• Audio / Video Call Support (#108)
• MQTT (#15)

Some strange features request in v1:

• Email/SMS/Push reminder for empty chat room (#155)

Some old feature issue worth looking at but not relevant: #189

Scenario

Put list of Scenario how developers will use this API

Portal Design

Remove this section if the feature have no Portal

API Design

Remove this section if the feature have no API

Open Questions

Put a list of open questions here before a complete design / specification is decided

Related Issues

• Server Issues
• Client Issues
• Guides Issues

[chpapa]

https://redis.io/topics/streams-intro

Redis now support streams which looks like the perfect DB for chat services?

• Each chatroom can be a stream, each user is a consumer and read to the stream (like pubsub)
• Seems reasonable easy to build offline cache sync with XRANGE
• Redis is very performant, read scaling can be handled by slaves, and chatroom could be sharded on cluster
• Redis can be configured to be persistent for this purpose
• Full text search need to be handled separately.