Infrastructure Overview
Infrastructure models — Shared (Heroku + S3) and Enterprise (dedicated AWS)
The SSM.ro platform's infrastructure differs depending on the deployment model. This page provides an overview; technical details are in the dedicated pages.
Differs by model
Shared Model (SaaS): the application runs on Heroku; AWS microservices (S3, API Gateway, Lambda, CloudWatch) run on shared infrastructure. Enterprise Model (Dedicated): dedicated AWS infrastructure per client (S3, API Gateway, Lambda, CloudWatch). See Deployment Models.
Platform Components (Shared Model)
| Layer | Component | Role |
|---|---|---|
| Edge | Heroku Router | TLS termination (Let's Encrypt), HTTPS enforced |
| Application | Web dynos | Web application, autoscaling |
| Asynchronous processing | Worker dynos | Signing, notifications, archive export |
| Database | Heroku Postgres | Relational data; PITR + daily snapshot |
| Cache / queue | Heroku Redis | Application cache + job queue |
| Document storage | AWS S3 (primary + CRR) | Document content; versioning + SSE |
AWS Services
Both models use AWS microservices (S3, API Gateway, Lambda, CloudWatch Logs). The difference lies in how they are allocated: shared infrastructure in the Shared Model, versus dedicated resources per client in the Enterprise Model. Details: AWS Services Used.
Related Pages
- Heroku Architecture — dynos, environments, pipeline, add-ons
- AWS Services — S3, IAM, CloudWatch
- Change and Configuration Management
- Operational Monitoring
For the complete data flows and diagrams, see System Architecture.