discord4j / connect

Distributed bot tools for Discord4J

Discord4J

Connect project offers a range of tools to set up a distributed bot architecture.

Work in progress. See Examples folder.

connect's Issues

Builders

For consistency between Discord4J and connect package, the components should be constructed with builders aswell.

Improve RabbitMQ Implementation

The current RabbitMQ implementation has a few flaws.

1. Add channel pooling: Currently for each call to RabbitMQ#send* methods a new channel is created
2. Connection Pooling (?) - What's the behaviour for the underlying connections of the channels?
3. Push messages to exchanges and not directly to the queues and let RabbitMQ do it's work
4. Add incremental backoff on error in the pipeline for send/receive

Support RabbitMQ by default implementation

Instead of just having RSocket and Kafka, make a default RabbitMQ implementation which uses fireproof RabbitMQ as exchange between Shard-Leaders and Shard-Workers.

TTL for unacknowledged messages

Current behaviour:
When no worker is available messages are queued infinitely in the payload-server.

Desired behaviour:
Give a TTL on startup/command to the payload server, which will drop messages after the given TTL.

Possible other solution:
Give a max queue size to the payload-server. So after the queue size is reached, messages are dropped with FIFO, so the oldest messages are about to be forgot first.