polizy-storage

Configure polizy storage adapters by implementing the StorageAdapter interface to persist authorization tuples. Use InMemoryStorageAdapter for local development and testing, then switch to PrismaAdapter for production database workloads.

The PrismaAdapter is recommended for polizy authorization in production. It supports multi-instance deployments and scales database workloads, whereas InMemoryStorageAdapter is strictly designed for development and testing scenarios.

Yes, you can build a custom storage adapter by adhering to the StorageAdapter interface. This allows you to design custom persistence logic for authorization tuples while maintaining compatibility with the polizy authorization framework.

Switch polizy storage from InMemory to Prisma by replacing the InMemoryStorageAdapter initialization with PrismaAdapter setup. This transition moves authorization tuple persistence from local memory to a production-grade database environment.

Yes, the Prisma storage adapter supports multi-instance production workloads. It is specifically guided for scalable deployments, ensuring authorization tuples are consistently persisted across multiple application instances.

When designing a custom authorization adapter, performance considerations include optimizing tuple persistence and retrieval logic within the StorageAdapter interface. Efficient adapter design ensures minimal latency during authorization checks across development and production environments.