Skip to main content

Platform Integration

Overview

Artos’s platform integration approach provides the “best of both worlds” - you get the benefits of continuous platform improvements and updates while maintaining full control over your custom systems and workflows. This approach ensures that your custom implementations benefit from core platform enhancements without requiring manual updates.

What is the “Best of Both Worlds” Approach?

The “best of both worlds” approach means that custom systems built on Artos automatically benefit from core platform updates while maintaining their unique customizations. This is achieved through a modular architecture that separates core functionality from custom implementations.

Key Benefits

  • Automatic Updates: Core platform improvements are automatically available to custom systems
  • Customization Preservation: Your unique customizations remain intact during platform updates
  • Reduced Maintenance: Less manual work required to keep systems up-to-date
  • Enhanced Security: Security patches and improvements are automatically applied
  • Performance Improvements: Core optimizations benefit all custom implementations

Core Architecture

Modular Design

Artos’s modular architecture consists of several layers:

Update Flow

Platform updates flow through the architecture:
  1. Core Platform Updates: Improvements to the core Artos platform
  2. Automatic Propagation: Updates automatically available to integration layer
  3. Custom System Benefits: Your custom systems benefit without code changes
  4. Backward Compatibility: Existing customizations continue to work

Workflow Integration

Artos workflows are the foundation for integrating AI-powered processing into your existing systems. A workflow combines custom agents (scripts with preset input/output fields) with connectors and post-processing steps to create powerful, automated data processing pipelines.

Understanding Workflows and Custom Agents

What are Custom Agents?

Custom agents in Artos are essentially scripts that have preset input and output field definitions. They act as the building blocks of workflows, each designed to perform specific tasks: Agent Structure:
  • Input Fields: Defined parameters that the agent expects to receive
  • Processing Logic: The core functionality that transforms input into output
  • Output Fields: Structured data that the agent produces
  • Validation Rules: Constraints on input/output data formats
Agent Types:
  • Data Processors: Transform and validate data structures
  • Content Analyzers: Extract insights from text or documents
  • Format Converters: Convert between different data formats
  • Quality Checkers: Validate data quality and consistency
  • Custom Logic: Domain-specific processing tailored to your needs

Creating Custom Agents

Custom agents can be created through the Artos platform interface or programmatically via the API:

Where Custom Agents Are Created

Custom agents can be created in several ways:
  1. Artos Dashboard: Visual interface for creating agents with drag-and-drop field definition
  2. API Integration: Programmatic creation via REST API calls
  3. SDK Methods: Using the Artos Python SDK for integrated development
  4. Workflow Builder: Created inline while building workflows
  5. Template Library: Start from pre-built templates and customize

Integration Patterns

Pattern 1: Direct API Integration

Integrate Artos directly into your existing workflows using the REST API:

Pattern 2: SDK Integration with Custom Agents

Use the Artos SDK for more advanced integration with custom agent creation:

Pattern 3: Event-Driven Integration

Integrate using webhooks and event-driven patterns:

Integration with Existing Systems

Database Integration

Message Queue Integration

Authentication and Authorization

API Key Management

Secure API Key Storage

Multi-Environment Support

Role-Based Access Control

Deployment Patterns

Containerized Deployment

Docker Integration

Kubernetes Deployment

Serverless Deployment

AWS Lambda Integration

Azure Functions Integration

Monitoring and Observability

Health Checks

Logging and Metrics

Best Practices

1. Security Best Practices

  • API Key Management: Store API keys securely using environment variables or secret management systems
  • Network Security: Use HTTPS for all API communications
  • Access Control: Implement role-based access control for different user types
  • Input Validation: Validate all input data before processing
  • Error Handling: Never expose sensitive information in error messages

2. Performance Best Practices

  • Connection Pooling: Reuse HTTP connections when possible
  • Caching: Cache frequently accessed data and workflow configurations
  • Batch Processing: Process data in batches for better efficiency
  • Async Processing: Use asynchronous processing for long-running operations
  • Resource Management: Monitor and optimize resource usage

3. Reliability Best Practices

  • Retry Logic: Implement exponential backoff for failed requests
  • Circuit Breakers: Use circuit breakers to prevent cascading failures
  • Health Checks: Implement comprehensive health checks
  • Monitoring: Set up monitoring and alerting for critical metrics
  • Backup Strategies: Implement backup and recovery procedures

4. Scalability Best Practices

  • Horizontal Scaling: Design for horizontal scaling from the start
  • Load Balancing: Use load balancers for distributing traffic
  • Database Optimization: Optimize database queries and connections
  • Caching Strategy: Implement appropriate caching strategies
  • Resource Limits: Set appropriate resource limits and quotas

5. Maintenance Best Practices

  • Version Management: Use semantic versioning for your integrations
  • Documentation: Maintain comprehensive documentation
  • Testing: Implement comprehensive testing strategies
  • Deployment: Use automated deployment pipelines
  • Monitoring: Continuously monitor system health and performance

Migration and Upgrade Guidance

Version Compatibility

Upgrade Procedures

Custom Agent Development Best Practices

Designing Effective Custom Agents

  1. Clear Input/Output Definitions: Define precise field schemas with validation rules and comprehensive documentation
  2. Single Responsibility: Each agent should have one clear, focused purpose to ensure maintainability
  3. Comprehensive Error Handling: Implement robust error handling with meaningful error messages and recovery strategies
  4. Performance Optimization: Consider processing time, memory usage, and resource efficiency
  5. Reusability: Design agents to be reusable across different workflows and use cases
  6. Security: Implement proper input validation and secure coding practices
  7. Documentation: Provide thorough documentation including examples and troubleshooting guides

Agent Testing and Validation

Agent Lifecycle Management

Summary

This comprehensive platform integration documentation provides the foundation for integrating Artos into existing systems while maintaining the benefits of continuous platform improvements. The focus on custom agents with preset input/output fields enables users to create powerful, reusable workflows that can be easily integrated into any system architecture.

Key Takeaways

  1. Custom Agents: Scripts with preset input/output fields provide predictable, type-safe integration points
  2. Workflow Flexibility: Combine agents, connectors, and post-processing for complex data pipelines
  3. Multiple Creation Methods: Dashboard, API, SDK, and template-based approaches serve different user needs
  4. Comprehensive Testing: Built-in testing and validation ensure reliability and performance
  5. Lifecycle Management: Full version control, deployment, and monitoring capabilities
  6. Integration Patterns: Support for API, SDK, event-driven, and database integration approaches
  7. Best Practices: Security, performance, and maintainability guidelines built into the platform
By following these patterns and best practices, organizations can successfully integrate Artos into their existing systems while maintaining the flexibility to adapt and scale as their needs evolve.