How droffilc1/devops-stage-4 works
Project type and purpose
• This is a microservice-based full-stack TODO application with user authentication.
• The root README describes five major components—Frontend (VueJS), Auth API (Go), TODOs API (NodeJS), Users API (Spring Boot/Java), and Log Message Processor (Python)—all wired together via Docker Compose.
File structure
• Top-level:
• docker-compose.yaml – orchestrates containers
• .env – environment variables (credentials, endpoints)
• frontend/ – VueJS single-page app
• auth-api/ – Go service issuing JWTs
• todos-api/ – NodeJS service for todo CRUD + Redis logging
• users-api/ – Spring Boot service exposing user profiles
• log-message-processor/ – Python worker reading from Redis
• Each service has its own Dockerfile and language-specific config (go.mod, pom.xml, package.json, requirements.txt).
• No shared code; services communicate over HTTP/REST and a Redis queue.
Extract insights from the README
• The README explicitly calls this “an example of microservice.”
• It outlines data flows:
• Frontend ↔ Auth API (login, JWT)
• Frontend ↔ Users API (fetch profiles)
• Frontend ↔ TODOs API (CRUD todos)
• TODOs API → Redis (queue “create”/“delete” events)
• Log Processor ← Redis (dequeues and logs to stdout)
Essential details
• Five services and their communication channels
• JWT token flow as the security backbone
• Redis-based logging pipeline
• Which services persist data and which rely on in-memory or runtime state