I was working on an app which serves roughly 400*10^6 API requests/day.
One cool property of our app is that it's rarely updated and mostly read.
And the goal is to achieve the lowest possible latency at the edge.
It scales beautiful, I am not sure which other architecture can help us keep this afloat with only 4 developers working on it.
So, we have a DynamoDB table which is replicated to multiple regions using DynamoDB streams and Lambda.
For us, Lambda means achieving a lot without many developers and system administrators but I understand that not all problems yield gracefully to this pattern.
It seems using Cloudflare Workers to trigger our Lambda function instead of API gateway could prove to be cheaper.
One cool property of our app is that it's rarely updated and mostly read.
And the goal is to achieve the lowest possible latency at the edge.
It scales beautiful, I am not sure which other architecture can help us keep this afloat with only 4 developers working on it.
So, we have a DynamoDB table which is replicated to multiple regions using DynamoDB streams and Lambda.
For us, Lambda means achieving a lot without many developers and system administrators but I understand that not all problems yield gracefully to this pattern.
It seems using Cloudflare Workers to trigger our Lambda function instead of API gateway could prove to be cheaper.