Software-as-a-Service (SaaS)
A cloud delivery model where applications are hosted centrally and delivered to customers as subscription services.
Classification
- ComplexityMedium
- Impact areaBusiness
- Decision typeArchitectural
- Organizational maturityIntermediate
Technical context
Principles & goals
Use cases & scenarios
Compromises
- Vendor lock-in via proprietary APIs or data formats.
- Security and compliance breaches due to misconfiguration.
- Cost explosion with inappropriate scaling strategy.
- Automated tests and canary releases for safe rollouts.
- Clear SLAs and transparent communication processes for customers.
- Data classification and segmentation to safeguard data sovereignty.
I/O & resources
- Application code and deployment artifacts
- Cloud infrastructure or platform services
- Security and compliance requirements
- Provisioned SaaS instance with monitoring
- Billing and usage reports
- Operational and support processes for customers
Description
Software-as-a-Service (SaaS) is a cloud delivery model where applications are hosted centrally and offered to customers as subscription services. Users access software over the internet while providers manage operations, scaling and updates. The model affects cost structures, integration patterns, security, and organizational responsibilities like tenancy and data ownership.
✔Benefits
- Faster customer access without local installation.
- Centralized operations and consistent updates.
- Scalability and flexible cost models via subscriptions.
✖Limitations
- Limited control over infrastructure and release timing.
- Challenges with specific integration requirements.
- Possible regulatory constraints regarding data residency.
Trade-offs
Metrics
- Availability (Uptime)
Percentage of time the service is reachable.
- Customer retention rate
Share of customers remaining active over a defined period.
- Operational cost per customer (OPEX per customer)
Average ongoing costs calculated per customer or tenant.
Examples & implementations
Office suites as SaaS
Productivity applications hosted centrally and offered by subscription.
Cloud CRM systems
Customer relationship management as a managed, multi-tenant service.
Industry software as hosted solution
Specialized applications operated centrally for many customers.
Implementation steps
Define strategy: target customers, multi-tenancy model and pricing.
Adapt architecture: design tenant isolation, scalability and observability.
Build infrastructure and CI/CD: set up automated provisioning and rollouts.
Implement security and compliance processes.
Migrate pilot customers and establish feedback loop.
⚠️ Technical debt & bottlenecks
Technical debt
- Short-term integrations implemented without standardization.
- Missing observability in critical paths.
- Monolithic architecture that becomes blocking for refactoring.
Known bottlenecks
Misuse examples
- Hosting an on-premise instance unchanged and calling it 'SaaS' without multi-tenancy.
- Compromising data security for speed to market.
- Omitting monitoring and SLAs in production customer environments.
Typical traps
- Underestimating data migration costs and complexity.
- Ignoring regulatory requirements in target markets.
- Hidden costs from misconfigured scaling.
Required skills
Architectural drivers
Constraints
- • Regulatory requirements for data sovereignty and location.
- • Dependency on cloud provider services and SLAs.
- • Requirement for reliable network and internet connectivity.