Hybrid Deployment
To help ensure the availability of your authorization service, Oso offers Fallback nodes. Oso Fallback nodes let you run a read-only copy of the Oso authorization service in your infrastructure, ensuring your application continues to authorize requests even if Oso Cloud becomes unreachable.
Oso Fallback nodes are read-only instances that are periodically updated with your environment's rules and data. This means they may be out of sync with the Oso Cloud during the interval between updates.
Because of this, Oso Fallback nodes are intended only as a last resort measure to ensure you can make authorization checks; they do not replace making authorization calls to Oso Cloud as part of normal operations.
Why do I need Oso Fallback?
Oso Cloud runs nodes at the edge across multiple regions and availability zones to ensure high availability (up to 99.99% uptime). Oso Cloud is designed to withstand multiple zone and regional outages without any customer-visible impact. We make this level of investment in availability and resilience to save you from having to do so – developing a high availability strategy, running the infrastructure, building the alerting, and so on.
However, no one has total control over services being partitioned away from one another, and even the most resilient applications can experience unavailability. We offer Oso Fallback because we understand that authorization is often on an application's critical path, and we take your application's availability seriously.
| Next Steps | Description |
|---|---|
| Set Up | Minimum requirements for deploying an Oso Fallback node and guidance on cluster configuration. |
| Configure | Toggles for configuring an Oso Fallback node. |
| Monitor | Understanding the performance, health, and usage of Oso Fallback. |
| Scale & Size | Ensuring Oso Fallback can support your production workload when you need it. |