-
Ally AI – API Gateway & Access Layer
Ally AI – Full Architecture Diagram ┌─────────────────────────────────────────────────────────────────┐ │ 1. USER REQUEST │ │ https://onyx.company.com/api/chat │ └──────────────────────────┬──────────────────────────────────────┘ │ ▼ ┌─────────────────────────────────────────────────────────────────┐ │ 2. LOAD BALANCER (GCP) │ │ Decision: "Which cluster?" │ │ – Checks geographic location │ │ – Checks cluster health │ │ – Forwards to US GKE cluster │ └──────────────────────────┬──────────────────────────────────────┘ │ ▼ ┌─────────────────────────────────────────────────────────────────┐ │ 3. GKE GATEWAY (Your Question) │ │ Decision: "Which service?" │ │ │ │ Questions GKE Gateway asks: │ │ ① What's the hostname? → onyx.company.com │ │ ② Does any rule match? → Yes, rule exists │ │ ③ What's the path? → /api/chat
-
Ally AI – Full Architecture Diagram
Ally AI – Full Architecture Diagram Full Architecture: Users & Administrators: Edge and Access Layer: Application Layer: Agent Capability: Secure RAG Query Path: Data And Search Services: Enterprise Knowledge Layer: Optional Advanced: AI and Model Layer: Typical Deployment Layer:
