Ory Oathkeeper Rule Store: Local File vs. etcd for Low-Traffic Workloads

Rule Store Configuration Trade-offs

When deploying Ory Oathkeeper for low-traffic environments, the choice of rule store impacts both infrastructure overhead and operational agility. The goal is to minimize resource consumption while maintaining a sustainable rule management process.

The local file rule store removes the need for external dependencies, significantly reducing memory and CPU footprints. However, this approach requires a service restart to apply rule changes. Conversely, the etcd rule store enables dynamic updates, but introduces the operational cost of maintaining an etcd cluster.

Given these constraints, it is unclear which approach is more efficient when rule updates are infrequent but cannot tolerate full service downtime.

• Does the etcd plugin support automatic rule reloading across all current stable releases without manual intervention?
• What is the specific resource overhead difference between a local file store and a single-node etcd instance in a minimal deployment?