How ssg192/sistemasismos works
Main Components
• Frontend: This is located in the “Desarrollo/Front” directory. It is a React-based application (with App.jsx, App.js, and MapaMexico.jsx) and uses an Nginx configuration for serving static assets. It interacts with the backend via HTTP requests.
• Backend: Found in “Desarrollo/Back/sismos”, this backend service is built using Java with Maven, Quarkus, and follows an MVC/microservices-style architecture. Within its package structure (mx.com.escom.sismos), it separates core business logic, REST controllers (SismoController), persistence (JPA with SismoDao, SismoJpaRepository), and utility components (state machine, error handling).
Relationships and Interactions
• The Backend connects to the Database by executing SQL scripts and using JPA/Hibernate to persist and retrieve data concerning seismic events.
• Docker Compose orchestrates the containers—likely one for the frontend, one for the backend, and one for the database—so include that as the deployment/operational layer.
Architectural Patterns and Key Technologies
• Layered Architecture: Break the backend into layers such as the REST Controller layer, service (business logic) layer, and persistence (repository/DAO) layer.
• Use of Quarkus: Emphasize that the backend is built with Quarkus and related technologies (JPA, Hibernate, RESTEasy Reactive).
• State Machine Integration: Show that the backend includes a state machine module for handling the lifecycle of seismic events.
• Docker Containers: The presence of multiple Dockerfiles (for frontend and backend) and a docker-compose.yml suggest containerization and orchestration.
• Frontend Framework: React is used for the client-side application, which is complemented by an Nginx server for static content.