However, after writing some code, I found that Fastly doesn’t allow for fetch requests to URLs not pre-defined in the application’s config.
While Compute@Edge feels like a great add-on to Fastly, it doesn’t quite fit the requirements for this full-stack application.
The developer experience for using Akamai’s edge workers is dramatically different than Fastly or Cloudflare.
To start, to even enable them on my account, I had to head to a Slack channel to ask for access.
Trying to set up the “Hello World” example they had, I had to jump through the hoops of enabling their “advanced TLS” and creating a certificate. This process is much more involved than with Cloudflare or Fastly.
For someone just looking to use a workers platform, I would not recommend Akamai as a solution.
Note: My experience may not be typical. Maybe something went wrong during onboarding. However, the point remains that Akamai’s developer experience is currently not up to par with that of Fastly or Cloudflare, and I prefer not to develop an application on their platform.
Building on Cloudflare Workers
While the developer experience on Cloudflare Workers isn’t perfect, it does get the job done without much fuss.
Setting up workers, creating a KV store for dev and prod environments, and deploying all happen without any challenges.