How zdarova69/microservice works
Project type and purpose
• This is a single microservice built with FastAPI (Python), fronted by Nginx as a reverse-proxy/load-balancer, and integrated with Kafka for asynchronous event streaming.
• The README confirms it’s an event-driven microservice: it exposes HTTP endpoints and publishes/consumes messages via Kafka.
(minimal) file structure
• Only README.md is shown, but based on the README we can infer a typical layout:
• app/ or src/ – FastAPI application code (routers, models, services)
• config/ – Nginx and Kafka configs (nginx.conf, docker-compose.yml)
• requirements.txt or pyproject.toml – Python dependencies
• Dockerfile(s) – to containerize the FastAPI app and Nginx
• scripts/ or infra/ – Kubernetes manifests or Docker Compose
README insights
• Tech stack: FastAPI (HTTP server), Nginx (reverse proxy), Kafka (message broker).
• Likely additional pieces: Uvicorn/Gunicorn worker, Docker, possibly a schema registry or Zookeeper (Kafka dependency) in dev/prod.