exa-migration-deep-dive
Execute Exa major re-architecture and migration strategies with strangler fig pattern. Use when migrating to or from Exa, performing major version upgrades, or re-platforming existing integrations to Exa. Trigger with phrases like "migrate exa", "exa migration", "switch to exa", "exa replatform", "exa upgrade major".
- License 许可
- MIT
- 最近更新
- 2026-05-26
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- exa-migration-deep-dive
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- version
- 1.0.0
- description
- Execute Exa major re-architecture and migration strategies with strangler fig pattern. Use when migrating to or from Exa, performing major version upgrades, or re-platforming existing integrations to Exa. Trigger with phrases like "migrate exa", "exa migration", "switch to exa", "exa replatform", "exa upgrade major".
- allowed-tools
- Read, Write, Edit, Bash(npm:*), Bash(node:*), Bash(kubectl:*)
- compatible-with
- claude-code, codex, openclaw
03 SKILL.md 正文
Exa Migration Deep Dive
Overview
Comprehensive guide for migrating to or from Exa, or major version upgrades.
Prerequisites
- Current system documentation
- Exa SDK installed
- Feature flag infrastructure
- Rollback strategy tested
Migration Types
| Type | Complexity | Duration | Risk |
|---|---|---|---|
| Fresh install | Low | Days | Low |
| From competitor | Medium | Weeks | Medium |
| Major version | Medium | Weeks | Medium |
| Full replatform | High | Months | High |
Pre-Migration Assessment
Step 1: Current State Analysis
set -euo pipefail
# Document current implementation
find . -name "*.ts" -o -name "*.py" | xargs grep -l "exa" > exa-files.txt
# Count integration points
wc -l exa-files.txt
# Identify dependencies
npm list | grep exa
pip freeze | grep exa
Step 2: Data Inventory
interface MigrationInventory {
dataTypes: string[];
recordCounts: Record<string, number>;
dependencies: string[];
integrationPoints: string[];
customizations: string[];
}
async function assessExaMigration(): Promise<MigrationInventory> {
return {
dataTypes: await getDataTypes(),
recordCounts: await getRecordCounts(),
dependencies: await analyzeDependencies(),
integrationPoints: await findIntegrationPoints(),
customizations: await documentCustomizations(),
};
}
Migration Strategy: Strangler Fig Pattern
Phase 1: Parallel Run
┌─────────────┐ ┌─────────────┐
│ Old │ │ New │
│ System │ ──▶ │ Exa │
│ (100%) │ │ (0%) │
└─────────────┘ └─────────────┘
Phase 2: Gradual Shift
┌─────────────┐ ┌─────────────┐
│ Old │ │ New │
│ (50%) │ ──▶ │ (50%) │
└─────────────┘ └─────────────┘
Phase 3: Complete
┌─────────────┐ ┌─────────────┐
│ Old │ │ New │
│ (0%) │ ──▶ │ (100%) │
└─────────────┘ └─────────────┘
Implementation Plan
Phase 1: Setup (Week 1-2)
set -euo pipefail
# Install Exa SDK
npm install @exa/sdk
# Configure credentials
cp .env.example .env.exa
# Edit with new credentials
# Verify connectivity
node -e "require('@exa/sdk').ping()"
Phase 2: Adapter Layer (Week 3-4)
// src/adapters/exa.ts
interface ServiceAdapter {
create(data: CreateInput): Promise<Resource>;
read(id: string): Promise<Resource>;
update(id: string, data: UpdateInput): Promise<Resource>;
delete(id: string): Promise<void>;
}
class ExaAdapter implements ServiceAdapter {
async create(data: CreateInput): Promise<Resource> {
const exaData = this.transform(data);
return exaClient.create(exaData);
}
private transform(data: CreateInput): ExaInput {
// Map from old format to Exa format
}
}
Phase 3: Data Migration (Week 5-6)
async function migrateExaData(): Promise<MigrationResult> {
const batchSize = 100;
let processed = 0;
let errors: MigrationError[] = [];
for await (const batch of oldSystem.iterateBatches(batchSize)) {
try {
const transformed = batch.map(transform);
await exaClient.batchCreate(transformed);
processed += batch.length;
} catch (error) {
errors.push({ batch, error });
}
// Progress update
console.log(`Migrated ${processed} records`);
}
return { processed, errors };
}
Phase 4: Traffic Shift (Week 7-8)
// Feature flag controlled traffic split
function getServiceAdapter(): ServiceAdapter {
const exaPercentage = getFeatureFlag('exa_migration_percentage');
if (Math.random() * 100 < exaPercentage) {
return new ExaAdapter();
}
return new LegacyAdapter();
}
Rollback Plan
set -euo pipefail
# Immediate rollback
kubectl set env deployment/app EXA_ENABLED=false
kubectl rollout restart deployment/app
# Data rollback (if needed)
./scripts/restore-from-backup.sh --date YYYY-MM-DD
# Verify rollback
curl https://app.yourcompany.com/health | jq '.services.exa'
Post-Migration Validation
async function validateExaMigration(): Promise<ValidationReport> {
const checks = [
{ name: 'Data count match', fn: checkDataCounts },
{ name: 'API functionality', fn: checkApiFunctionality },
{ name: 'Performance baseline', fn: checkPerformance },
{ name: 'Error rates', fn: checkErrorRates },
];
const results = await Promise.all(
checks.map(async c => ({ name: c.name, result: await c.fn() }))
);
return { checks: results, passed: results.every(r => r.result.success) };
}
Instructions
Assess current configuration
Document existing implementation and data inventory.
Step 2: Build Adapter Layer
Create abstraction layer for gradual migration.
Step 3: Migrate Data
Run batch data migration with error handling.
Step 4: Shift Traffic
Gradually route traffic to new Exa integration.
Output
- Migration assessment complete
- Adapter layer implemented
- Data migrated successfully
- Traffic fully shifted to Exa
Error Handling
| Issue | Cause | Solution |
|---|---|---|
| Data mismatch | Transform errors | Validate transform logic |
| Performance drop | No caching | Add caching layer |
| Rollback triggered | Errors spiked | Reduce traffic percentage |
| Validation failed | Missing data | Check batch processing |
Examples
Quick Migration Status
const status = await validateExaMigration();
console.log(`Migration ${status.passed ? 'PASSED' : 'FAILED'}`);
status.checks.forEach(c => console.log(` ${c.name}: ${c.result.success}`));
Resources
Flagship+ Skills
For advanced troubleshooting, see exa-advanced-troubleshooting.
04 同仓库更多 Skills
zustand-store-ts
Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.
zustand-store-creator
Zustand Store Creator - Auto-activating skill for Frontend Development. Triggers on: zustand store creator, zustand store creator Part of the Frontend Development skill category.
zero-trust-config-helper
Zero Trust Config Helper - Auto-activating skill for Security Advanced. Triggers on: zero trust config helper, zero trust config helper Part of the Security Advanced skill category.
zapier-integration-helper
Zapier Integration Helper - Auto-activating skill for Business Automation. Triggers on: zapier integration helper, zapier integration helper Part of the Business Automation skill category.
zai-cli
Execute z.AI CLI providing vision, search, reader, and GitHub exploration via CLI and MCP. Use when user needs image/video analysis, OCR, UI-to-code conversion, error diagnosis, real-time web search, web page to markdown extraction, or GitHub code exploration. Trigger with phrases like "analyze this image", "search the web for", "read this page", "explore this repo", or "use zai". Requires Z_AI_API_KEY.
yt-research
Research competitor YouTube channels, niches, and trending topics for your content strategy. Use this skill whenever the user says "research channels", "analyze competitors", "find trending topics", "niche analysis", "competitive research", "what are other creators doing", "scrape YouTube channels", or wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.