界面已本地化;技能介绍与说明文档按所选语言由 AI 自动翻译,代码、命令、路径和专业术语保留原文,以原作者文档为准。
探索技能
设计与创意 · SKILL.md

saas-architecture

saas-architecture

【设计与创意】Use when designing or building SaaS applications — multi-tenancy models (silo/pool/bridge), tenant isolation, subscription and billing integration (Stripe/Paddle), onboarding flows, feature flags and entitlements, usage metering, API rate limiting, tenant-aware data partitioning, SaaS operational patterns (noisy neighbor, tenant health), and SaaS sec…

独立 GitHub 快照 · 自动分类 · 以原作者文档为准

技能说明

GitHub

name: saas-architecture description: Use when designing or building SaaS applications — multi-tenancy models (silo/pool/bridge), tenant isolation, subscription and billing integration (Stripe/Paddle), onboarding flows, feature flags and entitlements, usage metering, API rate limiting, tenant-aware data partitioning, SaaS operational patterns (noisy neighbor, tenant health), and SaaS security (data isolation, compliance, SOC2).

SaaS Architecture & Patterns

Reference Files

Detailed code examples, patterns, and configuration are in the reference files below. Read the relevant file when working on that area.

FileCovers
billing-flags-onboarding-api.mdsubscription/billing integration (Stripe/Paddle), feature flags/entitlements, onboarding flows, and API design patterns
metering-operations-security.mdusage metering, operational patterns (scaling, deployment, monitoring), security/compliance, and anti-patterns
tenancy-isolation-partitioning.mdmulti-tenancy models (silo/pool/bridge), tenant isolation patterns, and data partitioning strategies

Anti-Patterns

Don'tWhy
Filter by tenant_id only in application codeOne missed filter = data leak. Use RLS + ORM filters as safety nets
Use a single API key for all tenantsCompromised key affects everyone. Keys must be tenant-scoped
Synchronously provision silo infrastructure on signupBlocks the request. Use async provisioning with status polling
Share encryption keys across tenantsOne breach exposes all tenants. Use per-tenant KMS keys
Delete tenant data without a grace periodNo recovery path. Always queue with 30+ day grace period
Skip webhook signature verificationSpoofed events can corrupt tenant state
Rate limit by IP instead of tenantMultiple tenants behind one IP get unfairly limited
Store plan/tier logic in the databaseDeployment-coupled. Define plans in code, store tenant-plan mapping in DB
Run migrations synchronously for schema-per-tenantLocks the request. Run async, report progress
Ignore noisy neighbor signalsOne tenant degrades experience for all shared-pool tenants
我的收藏