Akamai Developer Blog
developer.akamai.com · Company blog · on HN since 2013
Akamai's developer team writes about CDN features, edge computing, web performance measurement, DNS tools, and APIs.
What HN saysCommenters link it for Akamai's GraphQL caching, EdgeWorkers, HTTP/3 introduction, and the whoami DNS resolver tool.
15HN people shared it
9linked it in comments
6stories submitted
12story points
4 years agolast shared
2013people per year2026
Most-shared posts
- 1Measuring the Performance of Firefox Quantum with RUM1 people · 3 points · first shared 2017 · discussion on HN
- 2Akamai introduces new whoami tool for DNS resolver information1 people · 3 points · first shared 2018 · discussion on HN
- 3Akamai APIs - OPEN1 people · 2 points · first shared 2013 · discussion on HN
- 4Akamai Connector for Varnish out of beta1 people · 2 points · first shared 2017 · discussion on HN
- 5Akamai as Code with Jsonnet1 people · 1 points · first shared 2021 · discussion on HN
- 6Edge Compute – Akamai Developer1 people · 1 points · first shared 2021 · discussion on HN
- 7Introducing new whoami tool dns resolver information1 people · first shared 2020
- 8TCP Optimizations1 people · first shared 2016
- 9Akamai edgeworkers overview1 people · first shared 2022
- 10Introducing quic web content1 people · first shared 2019
- 11Solving options performance issue spas1 people · first shared 2021
- 12Tutorial 04 autoplay1 people · first shared 2019
- 13Mobile web performance monitoring conversion rate1 people · first shared 2018
- 14Quick introduction http31 people · first shared 2022
- 15Announcing graphql caching capability akamai api gateway1 people · first shared 2022
What HN people wrote when they linked it
bluesmoon · 2021-03-04
Another thing to note about custom headers is that when used in an XHR (eg: X-Requested-With), they will force a preflight request (with the OPTIONS method). If your webserver isn't configured to handle OPTIONS and return the correct CORS headers, that will effectively break clients.
Best to just never use custom headers.
I've written more about this here: https://developer.akamai.com/blog/2015/08/17/solving-options-performan…
thevarunraja · 2022-06-06
Akamai already solved this https://developer.akamai.com/blog/2019/06/18/announcing-graphql-cachin…
But looks like they will build more out of the box integrations.
cryptonym · 2022-02-16
Yes
You can do most thing with configuration. EdgeWorkers are also available if you want to run your own JS at the Edge https://developer.akamai.com/akamai-edgeworkers-overview
celsoazevedo · 2022-02-13
Major CDNs seem to be adopting HTTP/3 just fine:
Cloudflare: https://blog.cloudflare.com/http3-the-past-present-and-future/
Akamai: https://developer.akamai.com/blog/2020/04/14/quick-introduction-http3
Fastly: https://www.fastly.com/blog/why-fastly-loves-quic-http3
Not to mention Google, which uses it a lot for regular pages and for content (eg: YouTube video).
Adoption client-side also seems to be moving quickly too. I looked at the stats for 2 of my sites and HTTP/3 is now at 60-70%, with HTTP/2 having dropped to 25-30% already.
gslin · 2020-10-25
Akamai also provides something similar:
* https://developer.akamai.com/blog/2018/05/10/introducing-new-whoami-to…
jannes · 2019-10-28
No idea, but it seems to be using Akamai Player: https://player.akamai.com/
It seems to have an event called "autoplayblocked": https://developer.akamai.com/tools/AdaptiveMediaPlayer/docs/web/tutori…
baby · 2019-01-22
theyinwhy · 2018-08-01
It is a very convenient side effect and yes, users care a lot about load times as well, as multiple case studies show, eg. https://developer.akamai.com/blog/2015/09/01/mobile-web-performance-mo…
The reason users care is the reason people hop on amp.