Files
motovaultpro/docs/PLATFORM-SERVICES.md
2025-11-07 13:51:47 -06:00

80 lines
1.8 KiB
Markdown

# MVP Platform Module
## Overview
The MVP Platform module is fully integrated inside the MotoVaultPro backend container.
## Architecture
The platform module runs as part of the backend service:
- **Runtime**: `mvp-backend` container (Fastify API)
- **Shared Database**: Uses mvp-postgres
- **Shared Cache**: Uses mvp-redis
## Platform Capabilities
### Vehicle Data Service
The platform provides vehicle data capabilities including:
- Vehicle makes, models, trims
- Engine and transmission data
- VIN decoding
- Year-based vehicle information
**Data Source**: Vehicle data from standardized sources
**Cache Strategy**: Year-based hierarchical caching using mvp-redis
## Service Communication
### Application → Platform Communication
- **Protocol**: Internal service calls within the application
- **Database**: Shared mvp-postgres database
- **Cache**: Shared mvp-redis cache
## Deployment Strategy
### Integrated Deployment
The platform module deploys with the main application:
- Same deployment pipeline
- Shares database and cache
- Deployed as part of the five-container stack
## Integration Patterns
### Data Access
Application features access platform data through shared database:
- Direct database queries
- Shared cache for performance
- Single transaction context
## Troubleshooting
### Common Issues
**Service Discovery Problems**:
- Verify Docker networking: `docker network ls`
- Check backend container connectivity: `docker compose exec mvp-backend sh`
**Database Connection Issues**:
- Verify mvp-postgres is healthy
- Check port mappings and network connectivity
### Health Checks
**Verify Backend Service (contains platform module)**:
```bash
docker compose ps mvp-backend
```
### Logs and Debugging
**Service Logs**:
```bash
docker compose logs -f mvp-backend
```
**Database Logs**:
```bash
docker compose logs -f mvp-postgres
```