4) Detailed component deep dives (3 components)

This service's main responsibility is to orchestrate weather reporting functionalities.

Caching: The response from the API is stored in Redis with a Time-to-Live (TTL) to reduce vendor API calls and support cache invalidation.
Real-time Data Publishing: It's responsible for publishing events to Kafka for real-time processing and notifications.
Scalability via Kubernetes: Weather-Service is containerized and uses Kubernetes for auto-scaling, handling varying loads efficiently.
Outage Handling: In vendor outages, if data is in Redis, it returns cached data. If not, it queues requests for later processing.
Cache Check:When a request for weather data is received, the service first checks Redis cache to see if data already exists.
Vendor API Call: If data is not found, the service calls the third-party vendor API.

Subscribe to Kafka: Listens to Kafka topics published by Weather-Service for weather updates.
Message Processing: Processes messages to generate real-time notifications.
Notification Dispatch: Utilizes third-party services like Firebase, SMS gateways, and email services to send alerts to users.
Scalability: Can leverage Kubernetes or container orchestration frameworks to scale based on message load.

Vendor Integration: Handles API integrations, making the system vendor-agnostic.
Factory Design Pattern: Utilizes this pattern to dynamically select the appropriate vendor implementation at runtime.
Data Transformation: Converts vendor-specific data into a standardized format used internally.
Circuit Breaker Implementation: Ensures system reliability by preventing cascading failures from vendor outages.

Trade offs/Tech choices

Explain any trade offs you have made and why you made certain tech choices...

Polling:
- Pros: Simpler to implement, no need for maintaining a connection.
- Cons: Higher latency, inefficient on resources.
Push Notifications (e.g., Websockets, Firebase Cloud Messaging):
- Pros: Real-time updates, efficient use of resources.
- Cons: More complex infrastructure.

when our Thirdparty service providers have down time and we need to provide ssls simility to them to our client.