Razorpay's journey to microservices
Microservices are great but one of the biggest pain points of adopting them is Keeping Data Consistent across different databases.
The challenge becomes even steeper when we are dealing with Money; you just can't let a transaction go unnoticed, and hence to talk about it we have someone who has done it at scale - Arjun from Razorpay.
Here’s what we spoke about
Initial architecture/tech stack of Razorpay
ensuring strong consistency in a monolithic architecture
check constraints
deciding to move from monolith to microservices
splitting of databases/application logic when moving to microservices
dual writing of data into monolith and transaction outbox pattern
databases in the current microservice architecture
deciding on SQL vs NoSQL
ensuring consistency in a microservice architecture
payment flow with eventual consistency
prioritization for settlements@T+0
chaos testing
integration tests on the interface between 2 services
incidents when things went wrong
Here's the video 👇 do check it out
Thank you so much for reading 🖖 If you found this helpful, do spread the word about it on social media; it would mean the world to me.
If you liked this short essay, you might also like my courses and playlists on