Encore application architecture

Design the logical application before choosing directories and declarations. Apply the same architectural reasoning to Encore.ts and Encore.go; use encore-service or encore-go-service for language-specific implementation.

Read the application

Inspect the existing code and the Encore application model when available. Identify:

• User and system operations
• APIs, cron jobs, and Pub/Sub handlers
• Data models and the code that changes them
• Infrastructure resources and the services that use them
• Existing synchronous calls and event flows
• Failure, scaling, deployment, and security requirements

Preserve established application concepts unless the requested change requires redefining them.

Separate services from processes