Ashishkumar Pandey
10/10/2021, 12:05 AM<http://ap-south-1.dev.api.com|ap-south-1.dev.api.com>
, <http://us-west-1.dev.api.com|us-west-1.dev.api.com>
and <http://eu-south-1.dev.api.com|eu-south-1.dev.api.com>
. This would also create a problem of implementing some logic as to how to route requests from <http://dev.api.com|dev.api.com>
to the appropriate region. I believe Lambda@edge is one possible solution but how would I use it here? I could use it for routing requests to appropriate regions, I’ve heard of people doing that. I would love it if you awesome people could chime in with your opinions and experiences on how to build a global serverless API. Most of what I’ve read up involves people creating k8s clusters across multiple regions and using a service mesh such as Istio or Linkerd to coalesce those clusters together at L4. It would be great if we could figure out a L7 solution which needs minimal intervention / management.
I know, it’s a lot to ask, but I’d be grateful for any assistance.thdxr
10/10/2021, 12:12 AMthdxr
10/10/2021, 12:12 AMAshishkumar Pandey
10/10/2021, 12:14 AMAshishkumar Pandey
10/10/2021, 12:29 AMSimon Reilly
10/10/2021, 1:24 PMthdxr
10/10/2021, 7:27 PMAshishkumar Pandey
10/11/2021, 7:43 AM