gnz00

I prefer to write an initial implementation, and then in the testing process figure out which interfaces simplify my tests, and then I refactor the implementation to use those interfaces. Generally, this avoids unnecessary abstraction, as the interfaces for testing tend to be the same ones you might need for extensibility.

Ah cool, thanks for the update. I haven't looked at their stuff in over a year. Congrats on the launch, looks really slick.

This was at a fairly large enterprise that utilized Fastly, and has since switched to Akamai. We had many meetings with our AM and their architects to get access to their compute engine over multiple years but never could get them to open the doors. If I could migrate our GraphQL services to a new domain, I'd certainly try it out!

It's been awhile but IIRC you can't inspect the body on a POST request using Varnish. Either that or any real compute in Varnish gets super gnarly. I also think Fastly has a distributed K/V for state storage that you can access if you're using their new compute.

Man, we had this exact use case and a similar solution designed but we weren't able to get access to Fastly's new edge compute.

It doesn't seem to touch on the most glaring abuse in my opinion, which is the widgets on their search page that directly competes with websites bidding for page ranking.