Skip to content

Commit b9744b0

Browse files
committed
Update files and add agents-in-gcp post
1 parent ab9fc61 commit b9744b0

File tree

9 files changed

+223
-7
lines changed

9 files changed

+223
-7
lines changed

.DS_Store

10 KB
Binary file not shown.

CLAUDE.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
## Daily Notes Creation
2+
When asked to create a daily note or to-do list:
3+
1. Use template: `Templates/Daily Notes Template.md`
4+
2. Save to: `Daily Notes/YYYY/MM-MonthName/YYYY-MM-DD-DayName.md`
5+
- Example: `Daily Notes/2025/07-July/2025-07-14-Monday.md`

Users/prabha.arivalagan/Library/Mobile Documents/com~apple~CloudDocs/Documents/sada-projects/sada-ai-demo-bq-optimization-report/output_report/agent_2_partition/04-11-2025/partition_optimization_report_clean.pdf.md

Whitespace-only changes.

Users/prabha.arivalagan/Library/Mobile.md

Whitespace-only changes.

create_minimal_oas.py

Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
#!/usr/bin/env python3
2+
"""
3+
Create a minimal OpenAPI spec by keeping only essential operations
4+
"""
5+
6+
# Key sections to keep (line numbers from original file)
7+
essential_sections = [
8+
# Keep header (1-90)
9+
(1, 90),
10+
11+
# Keep tickets section (approximately lines 2000-5000)
12+
(2000, 5000),
13+
14+
# Keep users section (approximately lines 14000-16000)
15+
(14000, 16000),
16+
17+
# Keep organizations section (approximately lines 7000-9000)
18+
(7000, 9000),
19+
20+
# Keep components section (from line 15000 to end, but truncated)
21+
(15000, 25000),
22+
]
23+
24+
def extract_sections():
25+
with open('oas-backup.yaml', 'r') as f:
26+
lines = f.readlines()
27+
28+
extracted_lines = []
29+
30+
for start, end in essential_sections:
31+
if start <= len(lines):
32+
actual_end = min(end, len(lines))
33+
extracted_lines.extend(lines[start-1:actual_end])
34+
extracted_lines.append('\n') # Add separator
35+
36+
# Write minimal version
37+
with open('oas-minimal.yaml', 'w') as f:
38+
f.writelines(extracted_lines)
39+
40+
print(f"Created minimal OpenAPI spec with {len(extracted_lines)} lines")
41+
42+
if __name__ == '__main__':
43+
extract_sections()

docs/.DS_Store

8 KB
Binary file not shown.

docs/writing/.DS_Store

8 KB
Binary file not shown.
Lines changed: 175 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,175 @@
1+
---
2+
draft: false
3+
date: 2025-10-04
4+
slug: agents-in-gcp
5+
tags:
6+
- adk
7+
- agent-framework
8+
authors:
9+
- Prabha
10+
---
11+
12+
# Building AI Agents in Google Cloud: Choose the Right Approach for Your Needs
13+
14+
## TL;DR
15+
16+
- **ADK** → Google-developed open-source framework for building complex multi-agent systems with maximum control and modularity
17+
- **Conversational Agents (Dialogflow CX)** → Omnichannel customer conversations with structured flows and open-ended playbooks
18+
- **Open-Source Frameworks** → Leverage specific framework capabilities (LangChain's integrations, LangGraph's state management, CrewAI's collaboration) on GCP's managed infrastructure
19+
- **Agentspace** → Enterprise search platform and self-serve agent creation for automating everyday knowledge work tasks
20+
21+
**Key decision point:** Choose your building framework (ADK/Conversational Agents/Open-Source), then optionally deploy to Agentspace for enterprise wide access.
22+
---
23+
24+
Building AI agents in Google Cloud Platform presents four distinct paths, each optimized for different use cases. The challenge isn't finding options—it's choosing the right one.
25+
26+
This guide cuts through the complexity to help you make the right decision based on your specific business needs, not technical preferences.
27+
28+
## Decision Framework
29+
30+
31+
```mermaid
32+
flowchart TD
33+
Start{Type of Agent?} --> Path{Purpose?}
34+
Path -->|Conversational<br/>Chat & Voice| MultiTurn{Need multi-turn<br/>dialogues across<br/>channels?}
35+
MultiTurn -->|Yes| DialogFlow[Conversational Agents<br/>Dialogflow CX]
36+
MultiTurn -->|No| ADKCheck
37+
38+
Path -->|Agentic<br/>Workflows| ADKCheck{Building multi-agent<br/>systems with native<br/>GCP ecosystem?}
39+
ADKCheck -->|Yes| ADK[Build with ADK]
40+
ADKCheck -->|No| Framework{Want specific<br/>framework features?<br/>LangChain/LangGraph/<br/>CrewAI/AG2}
41+
Framework -->|Yes| OpenSource[Build with<br/>LangChain/LangGraph/<br/>CrewAI/AG2]
42+
Framework -->|No| ADK[Build with ADK]
43+
44+
ADK --> AgentEngine[Agent Engine<br/>Deployment]
45+
OpenSource --> AgentEngine
46+
```
47+
48+
49+
*Note: Agents deployed via Agent Engine and Conversational Agents can be integrated into Agentspace for organization-wide access
50+
51+
## Four Approaches to Building AI Agents in GCP
52+
53+
### 1. Agent Development Kit (ADK) - For Complex Multi-Agent Orchestration
54+
55+
**Best for:** Multi-agent workflows requiring complex routing and orchestration with programmatic control
56+
57+
ADK is Google's open-source framework for building sophisticated multi-agent systems with complete programmatic control.
58+
59+
**When to choose ADK:**
60+
- You need sophisticated multi-agent orchestration with hierarchical delegation
61+
- You need to orchestrate complex integrations with conditional logic and custom error handling across enterprise systems
62+
- Your use case involves backend automation or event-driven workflows (scheduled jobs, API-triggered processes, continuous monitoring) without user-initiated conversations
63+
64+
**Why ADK excels at this:**
65+
- Native GCP integration with built-in tools for BigQuery, AlloyDB, Cloud SQL, and direct access to Vertex AI services
66+
- Multimodal capabilities with documents, audio, and video, plus bidirectional streaming for real-time voice interactions
67+
- Modular architecture for independent agent development
68+
- 100+ enterprise connectors via Application Integration Toolset
69+
- Built-in evaluation framework (web UI, pytest, CLI) with CI/CD pipeline integration, step-by-step debugging with trace inspection, and comprehensive audit logging
70+
71+
**Not the right fit when:**
72+
- A simpler solution suffices - if you need a basic RAG bot or simple workflow, ADK may be overkill
73+
74+
**Example Business use cases where ADK excels:**
75+
- **Financial reporting** - Multi-source data aggregation, validation, and quarterly report generation triggered by schedule or events
76+
- **Insurance claim processing** - End-to-end claim automation with document extraction, policy validation, fraud detection, and intelligent routing
77+
- **Mortgage underwriting** - Document extraction agent, income verification agent, credit risk agent, and compliance agent coordinate with dynamic routing based on loan type, applicant profile, and regulatory requirements
78+
- **Incident response** - Real-time log analysis with root cause identification, automated rollbacks, and post-mortem generation
79+
80+
### 2. Conversational Agents (Dialogflow CX) - For Multi-turn conversation
81+
82+
**Best for:** Interactive user conversations requiring multi-turn dialogues across multiple channels chat, voice etc
83+
84+
Conversational Agents (Dialogflow CX) combines structured **flows** and open-ended **playbooks** for building customer service experiences across all channels.
85+
86+
**When to choose Conversational Agents:**
87+
- Your use case involves **conversational interactions with users** (customer support, sales, ordering, troubleshooting, IT helpdesk, etc.)
88+
- Users initiate conversations and expect natural, multi-turn dialogues
89+
- You need to serve conversations across multiple touchpoints (web chat, mobile app, phone/voice, contact centers)
90+
- Your conversations require both structured flows (predictable paths like order status checks) AND open-ended dialogues (general questions using knowledge bases)
91+
92+
**Why Conversational Agents excels at this:**
93+
- Flows (structured) and playbooks (open-ended) conversation patterns
94+
- Native omnichannel deployment with 30+ language support
95+
- Visual flow builders for non-technical users
96+
- Deep contact center integration
97+
98+
**Not the right fit when:**
99+
- Primary task is not conversational - better tools exist for backend automation or data processing
100+
- No multi-turn conversation flows - simpler solutions may suffice for one-off Q&A
101+
102+
**Business use cases where Conversational Agents excel:**
103+
- **Customer support** - Multi-turn conversations for order status, returns, and product questions across web, mobile, and phone
104+
- **Voice IVR** - Natural language phone interactions for account management with 30+ language support and telephony integration
105+
- **Restaurant ordering** - Conversational order-taking with menu navigation, customization, and payment collection
106+
- **Technical support** - Guided troubleshooting with state-managed diagnostic workflows and human handoff capabilities
107+
108+
### 3. Open-Source Frameworks on Vertex AI - For Framework-Specific Capabilities
109+
110+
**Best for:** Teams wanting specific framework features (LangChain's integrations, LangGraph's state management, CrewAI's collaboration, AG2's multi-agent patterns, LlamaIndex's RAG pipelines) on GCP's managed infrastructure
111+
112+
Vertex AI Agent Engine deploys your existing open-source framework code (LangChain, LangGraph, CrewAI, AG2, LlamaIndex) with managed infrastructure and deep GCP integrations.
113+
114+
**When to choose this path:**
115+
- You need specific framework capabilities (LangChain's 700+ integrations, LangGraph's state machines, CrewAI's role-based collaboration, AG2's multi-agent debates, LlamaIndex's advanced RAG)
116+
- You've already invested in framework codebases and want to deploy to production without rebuilding
117+
- You want rapid prototyping with framework-specific features (vector stores, document loaders, APIs, state management patterns)
118+
- You need GCP's managed infrastructure without abandoning framework expertise
119+
120+
**Why this excels:**
121+
- Leverage open-source framework capabilities on GCP's enterprise-grade managed infrastructure
122+
- Managed infrastructure with autoscaling
123+
- Enterprise-grade security and compliance built-in
124+
- Direct access to GCP services (BigQuery, Cloud SQL, etc.)
125+
- Dedicated SDK support for major frameworks
126+
- Access to Vertex AI Gen AI Evaluation service for agent performance assessment and trajectory analysis
127+
128+
**Not the right fit when:**
129+
- You don't need framework-specific features - ADK or Conversational Agents provide simpler, more streamlined solutions for GCP
130+
131+
**Business scenarios where you should use open-source frameworks:**
132+
- **RAG support bot** - Existing LangChain/LlamaIndex Q&A system with custom retrieval ready for production scaling
133+
- **Document analysis** - LlamaIndex investment with custom indices and query pipelines for contract analysis
134+
- **Research assistant** - LangGraph application with complex state management and human-in-the-loop workflows
135+
136+
137+
### 4. Google Agentspace - Enterprise Search & Agent Platform
138+
139+
**Best for:** Organizations needing enterprise-wide search across data sources and self-serve agent creation for everyday knowledge work tasks
140+
141+
Agentspace provides enterprise search across 100+ data sources and serves as a central hub for organizational agents. Enterprise Plus edition includes Agent Designer for creating no-code agents that automate everyday knowledge work.
142+
143+
**Key capabilities:**
144+
- Unified enterprise search across 100+ data sources (Microsoft SharePoint, Confluence, ServiceNow, Google Drive, etc.)
145+
- Self-serve Agent Designer for creating agents that automate everyday tasks (emails, scheduling, admin work) - Enterprise Plus edition
146+
- Central deployment hub ("From your company") for organizational agents from ADK, Dialogflow CX, and partner sources
147+
- Three editions: Enterprise, Enterprise Plus (includes Agent Designer), and Frontline
148+
149+
**When to choose Agentspace:**
150+
- You need enterprise-wide access to search and agents that respect individual user permissions and data access controls
151+
- Users want to automate simple day-to-day tasks (scheduling, emails, admin coordination) with permission-aware agents (requires Enterprise Plus for Agent Designer)
152+
- You need a central hub for deploying organizational agents from ADK (via Agent Engine), Dialogflow CX, and partner sources across the enterprise
153+
154+
155+
**Not the right fit when:**
156+
- Your agents serve external customers rather than internal employees - Use Conversational Agents or ADK with direct deployment
157+
- You need complex orchestration or advanced agent capabilities - Build with ADK, Dialogflow CX, or open-source frameworks first (can deploy to Agentspace later)
158+
- You don't need enterprise-wide agent discovery or user-permission-aware search - Deploy agents directly via Agent Engine or Dialogflow CX
159+
- Budget constraints with per-seat licensing model - Pay-per-use options (ADK, Vertex AI Agent Engine) may be more economical
160+
161+
## Side-by-Side Comparison
162+
163+
| Aspect | ADK (Google's Open-Source) | Open-Source Frameworks | Conversational Agents | Agentspace |
164+
|--------|-----|------------------------|----------------------|------------|
165+
| **Best For** | Build multi-agent systems | Build multi-agent systems | Interactive user conversations | Permission-aware enterprise search & agents |
166+
| **Development Approach** | Code-first | Code-first | Visual flow builder + Natural Language | Agent Designer (Enterprise Plus) |
167+
| **Key Strength** | Native GCP integration + multimodal | Based on Framework | Omnichannel support | User-permission-aware access |
168+
| **Hosting Platform** | Vertex AI Agent Engine | Vertex AI Agent Engine | Google-managed service | Google-managed service |
169+
170+
## Summary
171+
172+
Building AI agents in GCP comes down to choosing the right tool for your specific needs: ADK for multi-agent orchestration with native GCP integration, Conversational Agents for interactive dialogues across channels, Community Frameworks for leveraging specific framework capabilities, or Agentspace for enterprise-wide permission-aware search and agents.
173+
174+
All four approaches are production-ready and can work together—many organizations use multiple approaches for different use cases. Start with your use case, validate with a proof-of-concept, and focus on business value over technical complexity.
175+

requirements-doc.txt

Lines changed: 0 additions & 7 deletions
This file was deleted.

0 commit comments

Comments
 (0)