| description |
|---|
For low latency data transfers and for backups |
{% hint style="info" %} In this section, we will cover the different storages involved in the payment orchestration with Hyperswitch. {% endhint %}
Storage layer is built with caching layer and persistent storage. The goal is to provide low latency persistent storage at lower cost.
Redis cluster is used as the cache.
Any data that is accessed frequently but doesn't change often, is already cached in the router's memory. Payment related data is cached in the cache layer. Cache allows very low latency payments through hyperswitch.
Since Payment data should never be lost, the data is persisted in normal databases like Postgres. This allows hyperswitch to provide data related to payments, refunds, etc to the users on their dashboards.
The Payment related events are written to a queue (like kafka) and the drainers take the events and populate/update the persistent storage in near realtime. This allows hyperswitch to handle cache failures and provide near time view of payments data to users.