New billing primitives. Cost per invocation on functions and edge requests where it used to included in GB/h and bandwidth.
Cost per cache read and write instead of lumping it all in the bandwidth bill.
My reading is that the criticism of the bandwidth egress fees and it's inevitable unfavorable comparisons has hit home.
Only they were using that bucket for more than just egress. So they are breaking charges apart and this is going to have winners and losers from their customer base.
Reminds me of cloudflare pricing. They don't charge you bandwidth but do charge for invocations and if you do the math on how they bill invocations, the egress is in there - you are not escaping it. But the press of no egress fees is nice.
benreesman|1 year ago
I’m not doubting you at all, it’s just non-obvious to a non-serious user.
bcaxis|1 year ago
Cost per cache read and write instead of lumping it all in the bandwidth bill.
My reading is that the criticism of the bandwidth egress fees and it's inevitable unfavorable comparisons has hit home.
Only they were using that bucket for more than just egress. So they are breaking charges apart and this is going to have winners and losers from their customer base.
Reminds me of cloudflare pricing. They don't charge you bandwidth but do charge for invocations and if you do the math on how they bill invocations, the egress is in there - you are not escaping it. But the press of no egress fees is nice.