The goal of this project is for me to learn making an async messaging platform using go concurrency, websockets, and kafka. This project should prepare components that can run on a single laptop. Scaling is not the top priority here.
We first setup a server which listens on port 8080 for ws connections
- the server will send "success"
- the server will send timestamps every few seconds
- close connection when client is inactive
- will connect to the server
- will print messages it receives from the server
- support channels
- create an API to subscribe to a topic
the client will listen to topic
/subscribe/id:<uid>/topic:<topic>
- clients that are newly subscribed to a topic will only receive new messages
- use fanout to broadcast
- have one go routine per connection
- inter goroutine communicate via go channels
- create a shared struct between the separate goroutines
- decouple writer, reader, pinger, ponger
- topics mapping will be stored in mem and will be broadcased immediately - the serve* will not store messages for now
make an interactive client that looks something like below
> sub afrozalm:mala:zorfa
> attach afrozalm:mala:zorfa
> What\'s up all
> //
-----
$ tail -f afrozalm.mess
2021/05/13 16:00:14 [r/afrozalm:mala:zorfa]> (@afrozalm): What\'s up all
2021/05/13 16:00:31 [r/afrozalm:mala:zorfa]> (@zorfa): I\'m fantastic. Learning some magic tricks
2021/05/13 16:00:57 [r/afrozalm:mala:zorfa]> (@mala): Just finished RoW. My mind is blown into millions of pieces. BrandoSando is legend- Figure out why the messages to this long to arrive client
- Improve Logging.
- have multiple log levels
- control log levels via cli flags
- update client
- add attach: client need not always write the channel name followed by message
- add client level retries when server goes bust
- use kafka for inter server communication
- use proto buf for ser-deser
- place two servers behind nginx or HAProxy
- try out domain model by Kat