How bounswe/bounswe2025group6 works
File structure
• Currently the repo only has README.md; no code or folders are committed yet. Once code is added, pay special attention to:
• Top‑level directories (e.g., frontend/, backend/, mobile/, services/, docs/)
• Subdirectories indicating feature modules or layers (e.g., auth/, payments/, profile/)
• Configuration and deployment manifests (Dockerfile, docker-compose.yml, k8s/, .github/workflows/)
• Test folders (unit/, integration/, e2e/)
• Any infrastructure‑as‑code (terraform/, ansible/)
README and wiki for additional insights
• Look for sections on architecture, tech stack, and dependencies. The wiki will likely define:
• Whether this is a web app, mobile app, desktop app, API service, or some combination.
• The data flow (e.g., client → API gateway → microservice → database).
• Any third‑party services (e.g., AWS S3, Stripe, OAuth providers).
a. Main components (once known):
• Frontend: Web UI or Mobile clients
• Backend: API server(s), microservices, business logic
• Data stores: SQL/NoSQL databases, caches (Redis), message brokers (RabbitMQ, Kafka)
• External integrations: CI/CD, third‑party APIs, analytics
b. Relationships and data flow:
• Client requests → Load balancer or API gateway → Auth service → Core services → Database
• Asynchronous flows: service A → message queue → service B
c. Architectural patterns:
• Layered (presentation–business–data)
• Microservices vs. monolith
• Event‑driven or request/response
d. Call out key technologies:
• E.g., React or Angular for frontend, Node.js/Express or Spring Boot for backend, PostgreSQL, Docker, Kubernetes
Next steps
• Keep it living: update as the group adds new modules.