Re:AWS Lambda Edge changes duration billing granularity from...
by adreamingsoul on Saturday April 10, 2021 @01:23AM
(#26759138)
Varnish Cache with VCL allows you to create custom edge logic for things like header manipulation or backend selection.
Re:AWS Lambda Edge changes duration billing granularity from...
by jdub on Saturday April 10, 2021 @03:24AM
(#26759651)
Are you suggesting I build and maintain my own global CDN with 200+ edge locations? Thank you, but no thank you.
Re:AWS Lambda Edge changes duration billing granularity from...
by jcpham2 on Saturday April 10, 2021 @07:34AM
(#26760730)
I think so, as an alternative to all this AWS magic you could totally deploy <insert open source software name> on 200+ newly deployed instances, colo servers, or whatever you like!
I caught it too. I get downvoted a lot for not following rules and I don’t really care this was hilarious
Re:AWS Lambda Edge changes duration billing granularity from...
by adreamingsoul on Sunday April 11, 2021 @02:31AM
(#26767953)
cloud magic has shown us that “one day” we will need to scale up to an extreme count of “instances” and that suboptimal solutions can be negated with horizontal scaling.
In that phase you can change anything about the request itself, or the origin it will connect to. But the function only needs to run when there's a cache miss.
I have an application that needs to select an origin based on the request path (too many to use CloudFront cache behaviours), with a cache miss rate of less than 1%. It's a tiny amount of additional latency for cache misses, and a very small proportion of our CDN costs per month.