apify-reference-architecture

# Apify Reference Architecture ## Overview Production-ready architecture patterns for applications built on Apify. Covers standalone Actor projects, multi-Actor pipelines, and full-stack applications that integrate Apify as a data source. ## Architecture Pattern 1: Standalone Actor For a single scraper deployed to Apify platform. ``` my-scraper/ ├── .actor/ │ ├── actor.json # Actor metadata │ ├── INPUT_SCHEMA.json # Input definition (generates UI) │ └── Dockerfile # Build configuration ├── src/ │ ├── main.ts # Entry point (Actor.main) │ ├── routes/ │ │ ├── listing.ts # Router handler: listing pages │ │ └── detail.ts # Router handler: detail pages │ ├── types.ts # Input/output TypeScript types │ └── utils/ │ ├── extractors.ts # Data extraction functions │ └── validators.ts # Input/output validation ├── tests/ │ ├── extractors.test.ts # Unit tests for extraction logic │ └── integration.test.ts # Integration tests (live API) ├── storage/ # Local storage (git-ignored) ├── package.json ├── tsconfig.json └── .gitignore ``` ### Key Files ```typescript // src/main.ts — Actor entry point import { Actor } from 'apify'; import { CheerioCrawler } from 'crawlee'; import { router } from './routes/listing'; import { validateInput, ScraperInput } from './types'; await Actor.main(async () => { const rawInput = await Actor.getInput<ScraperInput>(); const inpu...