Architecture: What deployment architecture should we use for internal serv...

Documentation for Sessions

🏗️ Architecture: What deployment architecture should we use for internal serv...

Date: 2026-01-24
Time: 14:39:26 UTC
Session: editor2-64.2
Agent: documentation
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

What deployment architecture should we use for internal services vs user-generated platforms?

Task: Deployment infrastructure architecture

🎯 Decision Made

Chosen:

Separate pipelines: Railway for internal services, GitLab CI + Cloudflare Pages for user-generated platforms

Options Considered:

Single deployment pipeline for all
Separate pipelines: Railway for internal, GitLab+Cloudflare for users
Kubernetes for everything
Serverless-only approach

💭 Reasoning

Internal services (backend-api, backend-ai-api, backend-docs-api) require persistent containers, MongoDB connections, and specific environment configurations - Railway provides managed containers with easy GitHub integration via deploy branches. User-generated platforms are static Angular apps with SSR that benefit from edge hosting - Cloudflare Pages provides global CDN, automatic SSL, preview deployments, and ISR support. This separation allows independent scaling, different deployment frequencies, and optimized hosting for each use case.

📁 Files Involved

docs/english/Deployment/README.md
docs/english/Deployment/Internal/Railway/README.md
docs/english/Deployment/Platform-Users/README.md

🔗 Related

Decision ID: dev_1769265563009_b71xc6z
Session: 64
Workspace: editor2

Auto-generated by MCP Smart Consolidation