Legacy Memory

Legacy memory components provide backward compatibility with older memory systems and deprecated memory providers.

ZepChatMemory Component

This component creates a ZepChatMessageHistory instance, enabling storage and retrieval of chat messages using Zep, a memory server for Large Language Models (LLMs).

Usage

ZepChatMemory features:

• Legacy Zep integration

• Chat message persistence

• Session-based memory

• API-based access

• Backward compatibility

Inputs

Name	Type	Description
url	MessageText	URL of the Zep instance. Required.
api_key	SecretString	API Key for authentication with the Zep instance.
api_base_path	Dropdown	API version to use. Options: "api/v1" or "api/v2".
session_id	MessageText	Unique identifier for the chat session. Optional.

Outputs

Name	Type	Description
message_history	BaseChatMessageHistory	An instance of ZepChatMessageHistory for the session.

Legacy Support Features

Backward Compatibility

• API Version Support: Support for multiple API versions

• Migration Assistance: Tools for migrating to modern alternatives

• Deprecation Warnings: Notifications about deprecated features

• Documentation: Legacy-specific documentation

• Support Timeline: Clear support end-of-life timelines

Migration Path

• Modern Alternatives: Recommendations for current solutions

• Data Export: Export data from legacy systems

• Configuration Mapping: Map legacy configs to modern equivalents

• Testing Support: Tools for testing migrations

• Rollback Support: Safe rollback mechanisms

Deprecation Notice

⚠️ Important: This component is part of the legacy components collection and is no longer in active development. While it remains backward compatible and functional, we recommend migrating to modern memory alternatives:

Recommended Alternatives

For Cloud-Native Deployments

• Mem0 Chat Memory: Advanced cloud memory with AI-powered features

• AstraDB Chat Memory: Scalable cloud-native database memory

For Self-Hosted Deployments

• Cassandra Chat Memory: Enterprise-grade self-hosted memory

• Redis Chat Memory: High-performance in-memory storage

Migration Benefits

• Enhanced Performance: Modern alternatives offer better performance

• Improved Security: Updated security features and compliance

• Better Scalability: Modern horizontal scaling capabilities

• Active Support: Ongoing development and support

• Advanced Features: AI-powered memory management and search

Migration Guide

Step 1: Assessment

1. Inventory current Zep usage

2. Identify data requirements

3. Assess performance needs

4. Review security requirements

Step 2: Alternative Selection

1. Choose appropriate modern alternative

2. Review feature compatibility

3. Plan infrastructure requirements

4. Estimate migration effort

Step 3: Data Migration

1. Export data from Zep

2. Transform data format if needed

3. Import to new memory system

4. Validate data integrity

Step 4: Configuration Update

1. Update workflow configurations

2. Replace legacy components

3. Test new configurations

4. Monitor performance

Step 5: Cleanup

1. Archive legacy configurations

2. Remove deprecated components

3. Update documentation

4. Train team on new system

Transition Timeline

Phase 1: Parallel Operation (Recommended)

• Run both legacy and modern systems

• Gradually migrate workflows

• Compare performance and reliability

• Validate functionality

Phase 2: Primary Migration

• Switch primary traffic to modern system

• Keep legacy as backup

• Monitor for issues

• Address any gaps

Phase 3: Full Transition

• Decommission legacy system

• Complete data migration

• Update all documentation

• Remove legacy dependencies

Support Information

Current Support Level

• Bug Fixes: Critical bugs only

• Security Updates: Security patches as needed

• New Features: No new features

• Documentation: Maintenance mode only

End-of-Life Timeline

• Deprecation Date: Component marked as deprecated

• End of Support: No new bug fixes after this date

• End of Life: Component removed from platform

Getting Help

• Migration Support: Contact support for migration assistance

• Documentation: Legacy-specific migration guides

• Community: Community forums for peer support

• Professional Services: Migration consulting available

Usage Notes

• Legacy Status: This component is deprecated and not recommended for new projects

• Migration Priority: Plan migration to modern alternatives

• Support Limitations: Limited support for legacy components

• Documentation: Refer to current memory components for new implementations

• Testing: Thoroughly test migrations before production deployment

• Backup: Always backup data before migration attempts