ADK memory

​

Session services vs memory services

​

Set up ADK memory

​

Session service options

​

In-memory session service

​

Vertex AI session service

• project_id: Google Cloud project ID
• location: GCP region (for example, us-central1)
• reasoning_engine_app_name: Vertex AI Reasoning Engine application name

​

Database session service

agent:
  type: "ADK"
  config:
    session_service:
      type: "database"
      db_url: "postgresql://user:pass@localhost:5432/dbname"

​

Memory service options

​

In-memory memory service

​

Vertex AI memory service

• project_id: Google Cloud project ID
• location: GCP region
• memory_bank_resource_id: Vertex AI Memory Bank resource ID

​

Best practices

​

Session services

• Use in-memory for local development: No setup required, fast iteration
• Use Database for production: Reliable SQL-based persistence with multi-instance support
• Use Vertex AI for Google Cloud production: Cloud-native and scalable
• Configure session isolation: Each conversation should have a unique session ID to prevent state leakage

​

Memory services

• Use in-memory for development: Fast iteration, no external dependencies
• Use Vertex AI for production: Long-term persistence with semantic search capabilities
• Ingest session data into memory: Periodically move important information from sessions to long-term memory

​

General

• Separate concerns: Use session services for conversation state and memory services for long-term knowledge
• Monitor storage usage: Long-running sessions and large memory stores can consume significant resources
• Implement backup strategies: Set up regular backups for production database and Vertex AI configurations

​

Troubleshooting

​

Session service issues

1. Database connection errors: Use the Verify button on the memory configuration card to check connectivity. If the standalone runs in Docker and the database is on the host, use host.docker.internal instead of localhost
2. Vertex AI authentication: Verify Google Cloud credentials are configured and the service account has the required permissions
3. Session not persisting: Confirm the session service is initialized and session IDs are used consistently

​

Memory service issues

1. Vertex AI Memory Bank: Verify the Memory Bank resource ID is correct, the bank exists in the specified project and location, and IAM permissions are set
2. Memory not accessible: Confirm the memory service is initialized and its configuration matches your setup

​

General

1. Review logs: Check agent logs for session and memory-related errors
2. Check permissions: Verify the agent has access to all required storage resources
3. Verify configuration: Double-check all connection strings, credentials, and resource IDs

​

Next steps