chatrooms

How to Run

Use docker compose to run all required services:

    docker compose up

The application should be runnig of port 3000 after initialization (fiber header will appear).
There are some screenshots on the screenshots folder capturing the most important flows.
Note that this project uses jwt cookies for authentication, so to simulate multiple users you can:

• open multiple different browsers
• combine the use of private/icognito windows with normal windows, example

Contents

This command will run the following containers:

• Postgres: to persist application data (users, rooms, ...)
• RabbitMQ: to broker messages between servers and bots.
• ChatroomsServer: to handle the main application logic (register, posts, ...)
• ChatroomsBot: to process commands decoupled from main application logic

Notes

This application was developed with scaling of its individual components in mind:

• Commication between frontend client and server for real-time messaging uses the pub sub pattern. In this case there may be multiple instances of the server running (for scaling purposes) and the message broker will relay realtime messages to those subscribed to that rooms topic.

• Command processing uses the competing consumers pattern. In this case there may be multiple instances of bots running (for scaling purposes) and only one bot will respond to the command. The bots also have to acknowledge that the command was processed otherwise the message will return to the queue so other bots can process it. This ensures that if a bot goes down for any reason the message will not be lost.

Unit Testing

Tests were written for the controllers, utils and modes. Run them with:

  go test ./... -v

This tests also run on a github action workflow.
Note that the tests for the user controller take about 4 seconds.
That is a feature of bcrypt to prevent brute forcing passwords.