A List to Understand SaaS Architecture

This article was originally published on bmf-tech.com.

SaaSなんもわからん！からSaaS完全に理解した！に近づくために参考になりそうな資料をまとめておく。

Resources

• docs.aws.amazon.com - SaaS アーキテクチャの基礎
• docs.aws.amazon.com - SaaSレンズ
• docs.aws.amazon.com - SaaS Tenant Isolation Strategies: Isolating Resources in a Multi-Tenant Environment
• docs.aws.amazon.com - SaaS Storage Strategies
• d1.awsstatic.com - SaaS のテナント分離戦略
• speakerdeck.com - SaaS アーキテクチャ概要
• dev.classmethod.jp - [レポート] SaaSアーキテクチャーのパターンを学ぶ #reinvent #ARC306

Important Considerations for SaaS Architecture in Business Models

• Can flexible services (subscription plans, features, etc.) be provided to users?
• Can user onboarding (starting service use) be expedited?
• Can analytics, metrics, and billing be managed appropriately?
• Can non-functional requirements considering noisy neighbors be ensured?
• Can data breaches (such as data visible to other users between tenants) be appropriately addressed?
  • There are various methods to isolate resources used by tenants
  • cf. docs.aws.amazon.com - 基本的な分離の概念
• What are the resources to be isolated in terms of functionality, performance, data, etc.?

Thoughts

• Cost optimization seems challenging. If a specific tenant consumes excessive resources but the billing remains similar to other tenants, it could become problematic...
• There might be a need to share tenants between parent and subsidiary companies or partially integrate data, which could be tricky. There are trade-offs.