How jrandallsexton/sports-data-core works
Main Components Identification
The system consists of several microservices, each with specific responsibilities:
• API Gateway (entry point)
• Provider Service (external data collection)
• Producer Service (data transformation)
• Domain-specific services:
• Contest Service
• Franchise Service
• Notification Service
• Player Service
• Season Service
• Venue Service
• Shared Core Library
• Data Storage Systems
• Message Queue System (SNS/SQS)
Client Layer
• Web Clients
• Mobile Clients
• API Clients (Postman)
Service Layer
• API Gateway
• Identity Service
• Microservices Network
Infrastructure Layer
• Databases
• Message Queue
• Data Lake
Key Relationships to Highlight
a. Data Flow:
• External Sources → Provider → Data Lake
• Data Lake → Producer → Domain Services
• All Services ↔ Message Queue
• API Gateway → All Services
• Clients → API Gateway
b. Event-Driven Architecture:
• Event publishing/subscription patterns
• Central role of SNS/SQS
Technical Details
Infrastructure Components:
• Databases: Show per-service databases
• Message Queue: SNS/SQS implementation
• Data Lake: Storage for raw external data
• Docker containers: Show containerization boundary
• Kubernetes cluster: Indicate deployment boundary
Communication Patterns:
⇄ Bi-directional Communication
Deployment Context
• Docker containers
• Kubernetes pods
• Network boundaries
• Load balancers
• Azure pipeline integration
Additional Documentation
Annotations for:
• Scaling points
• Failure recovery paths
• Data consistency boundaries
• Service discovery mechanisms
• Health check implementations
Remember to highlight the event-driven nature of the system and how the Provider and Producer services act as the backbone for data ingestion and transformation, while domain services handle specific business logic areas.