How jth0809/aws_free_tier_microservice works
Main Components
• Budget Service (handles budgeting functionalities)
• Cache Service (manages caching operations)
• Edge Service (likely acts as an API gateway, interfacing with clients and forwarding requests)
• Location Service (manages travel or location-based operations)
• Member Service (handles user or member management)
• Post Service (manages posts, comments, and related content)
• Orchestration Service (coordinates multi-service transactions, ensuring data integrity)
• Supporting Infrastructure:
• Nginx: As a reverse proxy to route external requests to the respective services.
• Docker-Compose: Indicates the containerization and simplified local deployment orchestration tool.
• (Optional) AWS Components: Include AWS Free Tier services if needed, or mark that the services are deployed on an AWS environment.
• (Future Scope) Kubernetes: Note that a future migration to Kubernetes is planned.
Relationships and Interactions
• Possible asynchronous messaging flows (e.g., RabbitMQ references from the README) for tasks like content validation or cross-service events.
Architectural Patterns and Key Technologies
• Microservices Architecture: Emphasize independent deployability and separation of concerns.
• API Gateway: With the Edge Service and Nginx acting together to manage external communication.
• Containerization: All services are containerized using Docker, managed via Docker-Compose.
• Security & Configuration: Note that each service has its own security configuration (e.g., SecurityConfig classes in multiple modules) and that environment configuration is managed via the .env file.
• Messaging: There is a messaging package in several services (e.g., BudgetFunctions, PostFunctions, TransactionFunctions) indicating use of event-driven or messaging patterns.