Open-Source Project 2026 — Instant Messaging

ConnectFlow Messenger — Instant Messaging

Real-time platform supporting text, images, audio, and stickers, with JWT auth and a Docker + CI/CD production-ready architecture.

Year2026
RoleDesign, development, production architecture
StatusOpen source

Project Summary

ConnectFlow Messenger is a complete messaging platform built as a production-ready reference, with secure auth, multi-media support, and containerized deployment.

Real-timeJWTDockerCI/CD

The Problem

Most educational messaging projects succeed in showing a message on screen and then stop at the first real question: how do you build a platform that can actually be deployed, run securely and stay up? The gap is never in the chat interface — it is in the layers you cannot see: authentication, session handling, deployment topology and load testing.

ConnectFlow Messenger was built to cross that gap: a real-time messaging platform with JWT authentication and refreshable sessions, containerised with Docker and a CI/CD pipeline, so that "running it" becomes a documented step rather than a personal experiment.

Key Features

Instant messaging

Real-time text.

Multimedia

Images, audio, files, stickers.

JWT auth

Short-lived tokens with refresh.

Docker-ready

Compose files.

CI/CD

Automated test and deploy.

Scalable architecture

Separated services.

Technical Challenges & Design Decisions

  • Authentication between security and convenience: a short-lived access token protects the account but constantly logs the user out. The answer was a short access token plus a carefully handled refresh token, with real session invalidation on logout.
  • Delivery integrity: a live WebSocket loses messages when the network drops. Disconnect handling and automatic reconnection were added, while the message state stays visible to the user.
  • Reproducible deployment: running on the developer's machine does not mean it can be deployed. Packaging the stack in Docker with a CI/CD pipeline turned deployment from manual steps into one repeatable command.
  • Concurrency testing: real messaging bugs surface under concurrency rather than single-user use, so concurrency testing was part of development rather than a later stage.

Technical Architecture

Front endJWT authReal-timeStorage
Production architecture — front end, JWT auth layer, real-time messaging layer and storage, all automated with Docker and CI/CD
Backend API
Realtime Gateway
Media Store
JWT Auth
Docker & CI/CD

Testing Methodology

  • End-to-end authentication testing: sign-up, sign-in, token expiry, session refresh and logout.
  • Testing a dropped connection mid-conversation and verifying reconnection and continued message delivery.
  • Testing several concurrent connected users to confirm message-state consistency.
  • Verifying that a clean deploy from scratch works with exactly the documented steps and no manual setup.
  • Reviewing the interface in both light and dark themes and across screen sizes.

Outcome & Impact

  • A real-time messaging platform with hardened authentication and refreshable sessions running in containers.
  • One-command deployment through a CI/CD pipeline instead of error-prone manual steps.
  • A documented public repository that serves as a reference for teams working with the same architecture.

The project is released under the MIT licence; the code and deployment topology can be reviewed directly in the repository.