How alexlondon07/spring-boot-microservices-angular works
Main Components
• Frontend Client: Represent your Angular application. It is located in the “frontend” folder and interacts with the backend over HTTP/REST.
• API Gateways: There are at least two gateway services visible – “api-gateway-service” and “zuul-service.” These components route requests from the frontend to the appropriate microservices.
• Service Discovery: Mark the “eureka-service” as the service registry where all microservices register themselves dynamically.
• Domain Microservices: Include the various domain-specific microservices such as:
– answer-service
– exam-service
– course-service
– user-service
– common-exam, common-service, and common-student (for shared functionality)
• Database: Include a central or distributed database referenced by microservices (indicated by the “microservices_db.sql” file) if applicable.
• Inter-service Communication: Several microservices use Feign clients (for example, ExamFeignClient in answer-service and course-service) to communicate with each other. Represent these as connectors between services.
Relationships and Data Flow
• The gateways then use routing logic to forward these requests to the appropriate microservices based on URL paths.
• Additionally, if the gateways or any microservice directly accesses the database, label that connection.
Architectural Patterns and Design Principles
• Microservices Architecture: Clearly split the system into discrete, independently deployable services.
• Service Discovery: Use the “Eureka service” for dynamic discovery of microservices.
• API Gateway Pattern: Show a façade (by the gateways) that centralizes client requests and abstracts the complexity of the microservices.
• Resilience and Loose Coupling: While not visible explicitly in the file tree, the presence of multiple services and clients implies patterns such as circuit breakers, which might be used.
Technologies and Frameworks
• Spring Boot and Spring Cloud: For building microservices and for service discovery.
• Angular: For the frontend client.
• Maven: As the build and dependency management tool (visible via pom.xml and maven-wrapper scripts).
• Feign Clients: For inter-service communication.
• Also, note the use of Docker (as seen in some Dockerfiles), which might be included in the deployment or container orchestration context.