3 ms·
I'd love to see the architecture for this... Tho, I did hear they now have 200 lambdas a second firing to serve the content. That seems incorrect based on the e
by hactually 6y ago
I'd love to see the architecture for this... Tho, I did hear they now have 200 lambdas a second firing to serve the content. That seems incorrect based on the efforts on the caching layer.
Anyone else know more?
- qz2 6y agoThat's probably a very tiny fraction of their request footprint so it doesn't surprise me.
- k__ 6y agoThis. If you only got 100-1000 users, then 200 Lambdas per second is much. But if you got millions of users, it's not.
- willemlabu 6y agoFrom the article: > About 2,000 lambdas run every second to create the BBC website; a number that we expect to grow.
- robertlagrant 6y agoI sort of wonder why it isn't a content workflow in the background that triggers (say) a push to Fastly or Cloudflare to update a subset of cached content. Or maybe it is that, and that still takes 200 lambdas/sec.