chat-app-backend

README

chat-app-backend

Design

Users can login from any device(s), each devie may have multiple login sessons, so an unique client contains an ip and user.

No log policy for messages

Synchronization

We dont store messages in database, so it is important to backup your history regularly.

TODO: add backup and resotre feature

Devices initialization

When user connected to backend server from a sub device, a new websocket connection is established.

Whenever a message received from message queue, backend server will push it to any active connections.

Devices termination

When user terminate a sub device, all consumer with corresponding channel should be deleted, as well as the nsqd channel

Useful links

• scaling nsq
• implementing messaging queue nsq in golang using docker
• nsq and golang
• nsq design docs
• nsq with go
• golang nsq chat github repo
• realtime chat app using kafka springboot reactjs and websocket
• java kafka
• sending websocket messages to new clients(stackoverflow)
• should websocket server only handle get requests(stackoverflow)
• nsq requeue vs requeue without backoff
• socket io adapter
• blog
• nsq github distributed system issue
• gorilla websocket chat example(github)
• docker compose wait for container x before starting y(stackoverflow)
• ubuntu generate and retrieve root ca
• gist
• jwt blog
• jwt blog
• common anti patterns in go web applications
• p2p data sync for mobile
• Bramble Synchronisation Protocol
• gorm advanced query
• p2p im
• p2p im
• p2p im
• mobile p2p protocol
• p2p group
• p2p mq
• p2p mq
• gorm m2m
• gorm association
• api testing
• gorm uuid