How webcrunch/databaser-informationsstrukturer works
Project Type and Purpose
• This is an infrastructure-only Docker Compose stack for a database course environment.
• Purpose: stand up two relational databases (PostgreSQL, MySQL), two NoSQL databases (MongoDB, Redis), plus three web-based GUI tools for administration.
Main Components
a. Docker Host / Docker Engine (logical boundary)
b. Docker Network (the default bridge network or a custom network defined in docker-compose.yml)
c. Containers:
• postgres_db (PostgreSQL)
• mysql_db (MySQL)
• mongo_db (MongoDB)
• redis_cache (Redis)
• pgadmin (PostgreSQL GUI)
• mongo-express (MongoDB GUI)
• redisinsight (Redis GUI)
d. Future placeholder: app_server (for student application code)
e. External Users / Tools (e.g., DBeaver, MySQL Workbench, browser clients)
Relationships and Data Flows
• All containers communicate over the Docker network.
• External tools (on the host) connect via mapped host ports to each container.
• GUI containers talk internally (e.g., pgadmin → postgres_db).
• The future app_server would connect to each “_db” service by its service name.
Architectural Patterns & Principles
• Single Docker Compose file orchestrates multiple loosely coupled containers.
• Separation of concerns: each DB and GUI in its own container.
• Use of service names as DNS within the Docker network.
• Ports exposed to host for external tool connectivity.