Ah ok, I think I got it now.
So you point your DNS to fastly, and all requests initially go to the origin server if not in the cache.
You have some excludes for api calls that are always 'fresh'.
I want to get an idea on how many api calls are made to fastly for a site like this.
So they charge 0.0075 per 10K requests. = $0.75 per 1m API calls.
So say a given page makes 10 api calls, that is 10 million API calls per 1 million page views.
So the cost would be $7.5 per million page views.
For the 20% of requests that have to hit the origin server, I guess that cost is double since it has to make additional request to the origin server.
Is my math roughly correct? ~ $10 per million page views.
This is a cool hybrid approach when compared to serverless :)
Curious, how many and what kind of heroku instances does this puppy need?
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Ah ok, I think I got it now.
So you point your DNS to fastly, and all requests initially go to the origin server if not in the cache.
You have some excludes for api calls that are always 'fresh'.
I want to get an idea on how many api calls are made to fastly for a site like this.
So they charge 0.0075 per 10K requests.
= $0.75 per 1m API calls.
So say a given page makes 10 api calls, that is 10 million API calls per 1 million page views.
So the cost would be $7.5 per million page views.
For the 20% of requests that have to hit the origin server, I guess that cost is double since it has to make additional request to the origin server.
Is my math roughly correct? ~ $10 per million page views.
This is a cool hybrid approach when compared to serverless :)
Curious, how many and what kind of heroku instances does this puppy need?