This content originally appeared on DEV Community and was authored by Sibelius Seraphini
This article explains our decision-making at Woovi to use Redis.
Redis is a versatile database that can solve many problems when scaling a Fintech.
Cache
The first problem that Redis solves is to be able to cache data.
You can use cache to reduce the workload from external APIs or the main database.
We use it to cache slow/expensive external APIs, OAuth2 tokens, and account balances.
Distributed Lock
We use Redis to create distributed locks to make concurrency safe in some scenarios like updating the balance of an account.
Message Queue
We use Redis to create a message queue and async batch processing using BullMQ
Pub/Sub
We use Redis to create a publisher/subscriber to make our application real-time using WebSockets and GraphQL Subscriptions.
Rate Limiting
We also implement rate limiting using Redis to avoid DDoS attacks, Credential stuffing, Brute force attacks, and Data scraping.
In Conclusion
Redis is a versatile database that can be used in many scenarios to solve many problems as you scale.
If you are not using Redis, it could be a good addition to your tech stack
Woovi is an innovative startup revolutionizing the payment landscape. With Woovi, shoppers can enjoy the freedom to pay however they prefer. Our cutting-edge platform provides instant payment solutions, empowering merchants to accept orders and enhance their customer experience seamlessly.
If you're interested in joining our team, we're hiring! Check out our job openings at Woovi Careers.
Photo by Amélie Mourichon on Unsplash
This content originally appeared on DEV Community and was authored by Sibelius Seraphini
Sibelius Seraphini | Sciencx (2024-07-10T11:13:52+00:00) Redis at Woovi. Retrieved from https://www.scien.cx/2024/07/10/redis-at-woovi/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.