How Razorpay Migrated from Monolith to Microservices

Episode Summary

In our next episode, we are joined by Rajeev Rai, Principal Engineer, and Hemanth Venkata Muppuri, Software Developer at Razorpay as they discuss the challenges they overcame while migrating their core tech stack hosted on AWS to a microservices architecture using Redis Enterprise and Kubernetes. They also describe how they use Redis Bloomfilter for canary deployment and other use cases, including API rate limiting.

Episode Notes

[1:15]  Rajeev, can you tell us something about Razorpay as a company and what kind of business it is involved in?

[2:15] Rajeev, Can you tell us more about the overall architecture and technologies you use?

[3:30] Hemanth, what kind of challenges did you face with your existing tech stack? 

[5:10] Hemanth, what compelled you to switch to Redis and include it in your tech stack?

[6:25] Hemanth, Can you brief about Redis Bloom Filter to our listeners who are pretty new to this?

[9:20] ] Hemanth, What other Redis Use case are you using? 

[9:50] Hemanth, Can you drive deeper into the Rate Limiting side of things? 

[11:15] Rajeev, what are you the proudest of?

[14:00]: Rajeev, What do you like the most about Redis as a company as well as technology?

[15:35]: Rajeev, what do you want to do next with Redis?

Relevant Links:

Rate limiting

Bloom filters


Redis Mutex locks