Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/afrozalm/minimess
Created a generic messaging system on the lines of https://www.usenix.org/conference/srecon17americas/program/presentation/erlich
https://github.com/afrozalm/minimess
cassandra golang kafka
Last synced: 14 days ago
JSON representation
Created a generic messaging system on the lines of https://www.usenix.org/conference/srecon17americas/program/presentation/erlich
- Host: GitHub
- URL: https://github.com/afrozalm/minimess
- Owner: afrozalm
- Created: 2021-04-24T16:09:07.000Z (almost 4 years ago)
- Default Branch: master
- Last Pushed: 2021-07-11T10:18:48.000Z (over 3 years ago)
- Last Synced: 2024-11-19T22:50:23.808Z (3 months ago)
- Topics: cassandra, golang, kafka
- Language: Go
- Homepage:
- Size: 17 MB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# MINIMESS
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.
## 🟢 Phase 1
### Server related 1
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
### Client related
* will connect to the server
* will print messages it receives from the server
## 🟢 Phase 2
### Server related 2
* support channels
* create an API to subscribe to a topic
the client will listen to topic
/subscribe/id:``/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
## Client related 2
make an interactive client that looks something like below
```bash
> 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
```
## 🟢 Phase 3 goals
* 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
## 🟢 Phase 4 goals
* use kafka for inter server communication
* use proto buf for ser-deser
## Future Goals
* place two servers behind nginx or HAProxy
### misc goals
* try out domain model by [Kat](https://github.com/katzien/go-structure-examples)