How dsevilla/ssdd works
Main Components
• Frontend Components:
• “proyecto/frontend” and “ejemplos/frontend/flask-example”: These represent web UI components built with Python/Flask.
• “proyecto/llamachat”: A standalone chat application with its own Docker configurations.
• Backend Components:
• “proyecto/backend-grpc” and its example counterpart “ejemplos/backend/grpc”: These house gRPC-based services, each having client/server implementations and using protocol buffers (.proto files).
• “proyecto/backend-rest” (and its examples in “ejemplos/backend/rest-jersey”): Contain RESTful services likely implemented using Jersey.
• “proyecto/backend”: Provides additional backend functionality with DAO (data access objects) and business logic.
• Persistence and Databases:
• “proyecto/db-mongo” and “proyecto/db-mysql”: Docker configurations and initialization files for MongoDB and MySQL respectively, which serve as the data persistence layers.
• Common/Supporting Infrastructure:
• Docker and Docker-Compose files at the project’s root and in various folders signal containerized deployments.
• Build tools (like Maven with pom.xml files) and Makefiles indicate standardized build and deployment methods across components.
Relationships and Data Flow
• From the frontend side, illustrate two main UI systems (Flask-based web app and the chat app) that interact with the backend services through distinct API calls (gRPC calls for gRPC services, HTTP/REST for REST services).
• That the backend services interact with their designated databases (MongoDB for NoSQL operations and MySQL for relational data) using separate persistence modules (as seen with DAO implementations).
• That Docker-Compose setups tie these components together, suggesting networked communication between containers.
Architectural Patterns and Technologies
• Microservices or service-oriented architecture: Each backend module (gRPC, REST, DAO-driven services) is separated into its own service with clearly defined APIs and responsibilities.
• Containerization: Illustrate that each major component might run as a Docker container, referencing the multiple Dockerfiles and docker-compose configuration files.
• Technologies and frameworks: Label components with the precise technology used (e.g., Java with Maven for backend services, Jersey for REST, gRPC for RPC communication, Flask for the frontend, and Docker/Mongo/MySQL for persistence).