High availability architecture
Stigg’s mission is to create a reliable and highly available solution that won’t interrupt the mission-critical functionality of your application. To make sure that the critical paths are not affected, in case of a network error or if our services are unavailable for any reason, we have a few guardrails in place.
We prioritized the following SDK functions as “mission-critical”:
- Accessing customer entitlements (P95 latency <100ms)
- Reporting usage measurements (P95 latency ~200ms)
| Management API | Edge API | |
|---|---|---|
| Stack | Route 53 Application Load Balancer ECS, Fargate Amazon Aurora Global Database (PostgreSQL) SNS + SQS (Fanout) AWS Lambda | CloudFront AWS Lambda@Edge DynamoDB |
| Deployment | Multi A-Z Multi region (Active-Passive) Automated failover | Multi region (Managed by CloudFront) Automated failover |
| Uptime SLA | 99.99% | >99.9975% |
High availability architecture
Stigg’s mission is to create a reliable and highly available solution that won’t interrupt the mission-critical functionality of your application. To make sure that the critical paths are not affected, in case of a network error or if our services are unavailable for any reason, we have a few guardrails in place.
We prioritized the following SDK functions as “mission-critical”:
- Accessing customer entitlements (P95 latency <100ms)
- Reporting usage measurements (P95 latency ~200ms)
| Management API | Edge API | |
|---|---|---|
| Stack | Route 53 Application Load Balancer ECS, Fargate Amazon Aurora Global Database (PostgreSQL) SNS + SQS (Fanout) AWS Lambda | CloudFront AWS Lambda@Edge DynamoDB |
| Deployment | Multi A-Z Multi region (Active-Passive) Automated failover | Multi region (Managed by CloudFront) Automated failover |
| Uptime SLA | 99.99% | >99.9975% |