dblokhin / gong

An embedded message broker for Go

Gong

Lightweight and pretty simply embedded persistent message broker for golang projects.

publish -> topic -> stream -> consume

The goals

Features

• embedded lightweight, fast and reliable message broker with simple API
• multiple subscribers and publishers on topics
• named subscribers
• message headers support
• ??? message compressing
• ??? topic validator
• ??? pull/push subscription
• ??? masks

Examples

Benchmarks

How to contribute

gong's Issues

Make read journal for storage

Read journal is storage object for reading messages from filesystem maintaining reading offset.

• read journal initialized on subscribe()
• each subscriber has own read journal
• initial offset can be begining/end of topic

Add broker config

Headers support

Classical headers for transfer meta information with a message.

[tools] Add revive to project

Make PubManager

Make SubManager

With initial position: begining / end of topic.

Add more readable desctionpion/readme

Correct handle seqno overflow

Add license

GPL v2

Use broker signleton for single path

Use config MaxBatchSize parametr in batcher

c4 diagrams

Autocreation topic broker option

Connect write journal and read journal

• use somthing like ring buffer for sharing messages between publisher and subscribers (if seqno needed)
• read from filesystem only message doesn't exist in ring buffer

Add authors file

Create easy and good understangind broker API

Make write journal for storage

Write journal is a special storage object that is used for reliable placing messages to filesystem.

• one topic -> one write journal (doesn't matter how many publishers)
• write journal does only writes to filesystem through the batching mechanism
• initialized with first publish()
• write() is syncronious call for caller