How nithack/interview-agibank works
Main Components
• Client Service API: This microservice manages customer data with full CRUD operations.
• Insurance Service API: This microservice handles both the simulation and actual contracting of insurance policies (Bronze, Silver, Gold). It internally interacts with the Client Service API to validate client existence.
• PostgreSQL Database: Serves as the persistent store for client and insurance data.
• Docker & Deployment: Docker Compose, Dockerfiles, and the build script (build.sh) provide the containers and build automation for the distribution of services.
• (Optional) External Interfaces: Swagger for API documentation, and testing tools (JUnit, Mockito) used for unit/integration tests.
Relationships and Interactions
• Docker Compose orchestrates the containerized environment, so include a container orchestration element that groups client-service-api, insurance-service-api, and Postgres, along with directional dependencies (e.g., insurance-service-api depends on client-service-api and postgres).
Architectural Patterns and Design Principles
• That both services adhere to SOLID principles and Code Clean practices, which are key in maintaining clear separation of concerns.
• How API gateways (Swagger UI access points) might interact externally (via HTTP ports such as 3030 for client and 3031 for insurance).
Relevant Technologies, Frameworks, and Tools
• Java 17, Maven, and Spring Boot (implied by Maven and the use of Spring commands in the README).
• Docker, Docker Compose are used to package and deploy.
• PostgreSQL as the database.
• Testing frameworks: JUnit 5 and Mockito.
• Swagger for API documentation.