How Freshworks Scaled from 30 to 500 Million Requests Per Day
Failed to add items
Sorry, we are unable to add the item because your shopping cart is already at capacity.
Add to basket failed.
Please try again later
Add to Wish List failed.
Please try again later
Remove from Wish List failed.
Please try again later
Follow podcast failed
Unfollow podcast failed
How Freshworks Scaled from 30 to 500 Million Requests Per Day
-
Narrated by:
-
By:
About this listen
[1:30] Vijay can you tell us about Freshworks?
[3:00] What have you done with Redis?
[4:00] How do you choose technology/databases?
[8:45] How do you deploy?
[12:45] Tell us more about your “main Redis” use case
[14:50] Do you have an idea of operations per second?
[17:45] Did you do the migration live?
[18:05] How does Freshworks leverage the Bloom filter?
[17:00] What made you migrate from Elastic Cache?
[20:50] Any other use case you want to highlight?
[23:25] Why Freshworks uses the Lua script
[24:50] What to come next?
[26:10] What are you the proudest of in your project?
[27:30] How do you keep your developers engage?
Relevant Links:
Freshworks.com
Freshworks Use Case
Basic Rate Limiting Best Practices
RedisBloom
What listeners say about How Freshworks Scaled from 30 to 500 Million Requests Per Day
Average Customer RatingsReviews - Please select the tabs below to change the source of reviews.
In the spirit of reconciliation, Audible acknowledges the Traditional Custodians of country throughout Australia and their connections to land, sea and community. We pay our respect to their elders past and present and extend that respect to all Aboriginal and Torres Strait Islander peoples today.