Stigg home page
Search...
⌘K
Ask AI
Status
Product updates
Go to Stigg
Go to Stigg
Search...
Navigation
Getting usage data into Stigg
Scalability and durability
Home
Documentation
Guides
API & SDKs
FAQ
Getting started
Welcome to Stigg
Getting started in minutes
Modeling your pricing in Stigg
Overview
Features
Products
Plans
Add-ons
Coupons
Managing customers & subscriptions
Customers
Subscriptions
Subscription upgrades & downgrades
Provisioning bespoke subscriptions using AI
Getting usage data into Stigg
Overview
Reporting calculated usage
Reporting raw events
Viewing usage events
Handling reported usage
Scalability and durability
Snap-in widgets
Overview
Pricing table
Customer portal
Checkout
Native integrations
Overview
Billing
CRM
Data warehouses
Marketplaces
Authentication
Webhooks
Durable queues (SQS)
Importing and exporting data
Importing existing customers and subscriptions
Exporting data from Stigg
Going live
Go-live checklist
Workflow automation
Overview
Key concepts
Supported workflow nodes
Workflow creation
Error handling
Workflow execution
Managing workflows
Workflow credentials
Rolling out pricing changes with confidence
Gaining insights about your pricing strategy
Running pricing experiments
Price localization
Price localization overview
No-code configuration in the Stigg Console
Implementing price localization on your public website and application
Localized billing
Managing your account
Account details
Environments
Access management
Finding entities
Activity log
Switching accounts
Theme
Billing
High-availability and scale
High availability architecture
Accessible from anywhere
Local caching and fallback strategy
Persistent caching
Sidecar
Errors, retries, and usage buffering
Reliability, observability and monitoring
Security & compliance
Security Portal
Terms of Use
Privacy policy
Conceptual guides
Domain model
On this page
Scalability
Durability and recovery
Getting usage data into Stigg
Scalability and durability
Scalability
Stigg’s metering and aggregation capabilities are designed from the ground up for managing high-volume real-time use cases:
The Stigg API and SDKs allow you to report usage events in batches, with up to 1000 events per batch.
Usage events can be reported in parallel from multiple distributed reporters without requiring any coordination.
Built-in idempotency guarantees that duplicate events are only reported once.
Current usage is accessed from a
distributed cache
and is automatically replicated across multiple regions.
Local caching
allows you to access reported usage without needing to make a call over the network.
If you’re expected to report more than 1000 events per second
let us know
.
Durability and recovery
Reported usage events are stored in their original format in a highly available persistent data store with 99.999999999% of durability. This is allows you to rebuild usage data from scratch at any point in time if needed.
Handling reported usage
Overview
Assistant
Responses are generated using AI and may contain mistakes.