Update README.md

README.md

@@ -126,44 +126,4 @@ print(plantuml_code)
 
 ![image/png](https://cdn-uploads.huggingface.co/production/uploads/65be16980a0c57943fbe8b00/npfHv8F3MzHHWlvmwRge0.png)
 
-## Eval Q2
-**Question:**  
-*"Generate a PlantUML diagram that visualizes a microservices-based e-commerce architecture with the following components and relationships:  
-
-1. **Frontend Services:**  
-   - A React-based 'Storefront' app (handles product listings, cart, and checkout).  
-   - An Angular-based 'Admin Dashboard' (for inventory, orders, and analytics).  
-   - Both interact with an 'API Gateway' (Kong) that routes requests to backend services.  
-
-2. **Backend Services:**  
-   - 'Product Service' (manages SKUs, pricing, and inventory; uses PostgreSQL).  
-   - 'Order Service' (processes transactions, integrates with Stripe/PayPal; uses MongoDB).  
-   - 'User Service' (handles authentication via JWT/OAuth2; Redis cache for sessions).  
-   - 'Recommendation Service' (ML-driven, trained via TensorFlow; pulls data from a Kafka stream).  
-   - 'Notification Service' (email/SMS alerts via AWS SNS).  
-
-3. **Supporting Infrastructure:**  
-   - Docker containers orchestrated via Kubernetes (with labeled nodes for 'prod' and 'staging').  
-   - CI/CD pipeline (GitHub Actions → Docker Hub → ArgoCD for deployments).  
-   - Monitoring stack (Prometheus + Grafana, with custom dashboards per service).  
-   - External dependencies (Stripe API, Twilio API, and a legacy ERP system exposed via REST).  
-
-4. **Data Flow:**  
-   - Async communication between services via RabbitMQ (e.g., order confirmations → notifications).  
-   - Event sourcing for 'Order Service' using Kafka (commands vs. events).  
-   - CQRS pattern separating read/write databases for 'Product Service.'  
-
-5. **Security & Observability:**  
-   - TLS/mTLS between services.  
-   - Istio for service mesh (with circuit breakers and retries).  
-   - Distributed tracing (Jaeger) and structured logging (ELK stack).  
-
-**Additional Requirements:**  
-   - Color-code services by domain (e.g., yellow for payment, green for inventory).  
-   - Annotate critical interactions (e.g., 'HTTP POST /orders').  
-   - Include a legend explaining symbols (containers, queues, databases).  
-   - Optionally, overlay a sequence diagram snippet showing the 'checkout flow' (user → API Gateway → Order Service → Payment → Notification)."*  
-
-
-![image/png](https://cdn-uploads.huggingface.co/production/uploads/65be16980a0c57943fbe8b00/9HvxQNfhP7mULzB51ULuv.png)