Framework Templates

APSO supports multiple backend frameworks. Choose the one that best fits your team’s expertise and project requirements.

Available Frameworks

Framework Comparison

Choosing a Framework

TypeScript (NestJS)

Best for:

• Teams with JavaScript/TypeScript experience
• Complex enterprise applications
• Full-stack JavaScript stacks
• Strong typing requirements

Python (FastAPI)

Best for:

• Data science teams
• Machine learning integrations
• Quick prototyping
• Teams with Python experience

Go (Gin)

Best for:

• High-performance requirements
• Microservices architectures
• Resource-constrained environments
• Teams with Go experience

Generated Code Structure

All frameworks follow a similar structure:

src/
├── entities/           # Database entities
├── modules/            # Feature modules
│   ├── {entity}/
│   │   ├── controller  # HTTP handlers
│   │   ├── service     # Business logic
│   │   └── dto/        # Data transfer objects
├── extensions/         # Your custom code
├── config/             # Configuration
└── main.*              # Entry point

Customization

All generated code is yours to customize:

1. Extensions Pattern — Add custom endpoints without modifying generated code
2. Partial Generation — Regenerate only what you need
3. Eject Mode — Take full control of the codebase

Framework-Specific Features

TypeScript Features

• Decorators for routing and validation
• Dependency injection
• Swagger/OpenAPI auto-generation
• Jest testing setup

Python Features

• Pydantic models for validation
• Async/await throughout
• Auto-generated OpenAPI docs
• pytest configuration

Go Features

• Middleware support
• Struct tags for validation
• Swagger generation
• Go testing utilities

Switching Frameworks

Currently, switching frameworks requires creating a new service. Your schema (.apsorc) is framework-agnostic and can be reused.

Related

• TypeScript Guide →
• Python Guide →
• Go Guide →