Understand the core architecture and components of Julep
Julep Architecture Overview
System Architecture
The main orchestrator of your application, backed by foundation models like GPT4 or Claude.
Users can be associated with sessions and are used to scope memories formed by agents.
The main workhorse for Julep apps.
Programmatic interfaces that foundation models can “call” with inputs.
Collections of text snippets indexed into a vector database.
Github Actions-style workflows for complex operations.
Encrypted key-value pairs for securely storing sensitive information like API keys and credentials.
The document store provides a vector database for semantic search along with a document management system. It supports various file types and handles automatic indexing and retrieval of documents.
The task execution engine handles distributed task processing, state management, error handling with retries, and supports parallel execution of tasks.
The secrets store provides encrypted storage for sensitive information like API keys, credentials, and tokens. It uses AES-256 encryption and developer-scoped access controls to securely manage confidential data.
The API layer provides RESTful API endpoints, SDK support, authentication and authorization capabilities, and handles rate limiting and quotas.
Data Flow Overview
The data flow in Julep is divided into three main components, each handling specific aspects of request processing and response generation.
Client Interaction
Task Processing
Response Handling