zelshahawy/anonymous repository overview

Here’s a high-level overview of your containerized microservices app:

Purpose Provide an anonymous chat platform with real-time messaging, user authentication, and an integrated finance query service.

Core Components

• MongoDB (mongo:6)

  • Persists user profiles, chat histories, and session data.
  • Exposed on port 27017 and backed by a Docker volume for durability.

• Backend (zelshahawy/myapp:backend-latest)

  • Go-based REST & WebSocket server handling authentication, message routing, and data access.
  • Reads secrets and config from an .env file.
  • Listens on port 8080.

• Frontend (zelshahawy/myapp:frontend-latest)

  • Next.js/React SPA that manages login, chat UI, and real-time updates via WebSockets.
  • Uses environment variables to point at your backend endpoints.
  • Served on port 3000.

• Finance Microservice (zelshahawy/myapp:python-latest)

  • Python Flask (or FastAPI) service exposing stock-quote and analysis endpoints.
  • Consumes market‐data APIs and can be invoked via chat commands.
  • Runs on port 5005.

Architecture & Orchestration

• All four services are defined in a single docker-compose.yml (v3.8).
• Each custom service is built locally and tagged under one Docker Hub repo (zelshahawy/myapp) with distinct tags (backend-latest, frontend-latest, python-latest).
• Compose ensures correct startup order with depends_on, so Mongo starts first, then the backend, then frontend and Python service.

Deployment Workflow

1. Login & build

   docker login
   docker compose build
   

   Copy

2. Push all images (to your single “myapp” repo):

   docker compose push
   

   Copy

3. Run the stack (locally or on any Docker host):

   docker compose up -d
   

   Copy

   —this brings up your entire anonymous-chat + finance app in one go.

With this setup, you manage and version all three custom services in a single Docker Hub repository, while keeping each component isolated and scalable.