3 ms·
Thank you for taking time to reply. What does the roadmap look like around establishing some sort of multi-tier architecture within the CF product stack? I im
by bob1029 3y ago
Thank you for taking time to reply.
What does the roadmap look like around establishing some sort of multi-tier architecture within the CF product stack?
I imagine I could hack something together today by combining CF workers and another hyperscaler to run my .NET workload (TCP connection definitely helps with this!), but I think that there would still be a lot of friction with operations, networking, etc at scale. Ideally, workers and backend would be automagically latency-optimized and scaled relative to each other.
- kentonv 3y agoIt's definitely something we're thinking about but I don't have any sort of timeline, sorry.
- Manouchehri 3y agoWe use Workers with AWS Lambdas when a container is required. https://github.com/aimoda/cloudflare-worker-to-aws-lambda-function-url-example https://github.com/aimoda/cloudflare-worker-to-aws-lambda-fu... We don't have this in any public example yet, but here's our simple trick with Workers on how to bypass needing to pay for Amazon API Gateway or CloudFront but still get routed to the nearest AWS location: 1. Add add Lambda Function URLs as records in a latency based record on Route 53. (Lambda Function URLs do not support custom domains, so you cannot use this record directly.) 2. Have the Worker do a fetch to `https://cloudflare-dns.com/dns-query https://cloudflare-dns.com/dns-query` on the Route 53 CNAME to discover what lowest latency Lambda Function URL hostname is. 3. The Worker can then fetch the Lambda Function URL using the discovered hostname.