AWS Lambda pricing vs Google Cloud Functions pricing, explained

It is not simple to understand the complexity in the pricing model in AWS and Google Cloud Cloud Functions and why never is easy to understand how much I am going to expend.
#awslambda #googlecloudfunctions #finops #cloudcosts
* See more on Lambda costs in the behind the scenes of mkdev's job processing pipeline: mkdev.me/posts/processing-bac...
💸 Let us do a comprehensive cloud cost audit for you, for free - mkdev.me/b/audits/in-depth-aw... or schedule a call directly here: mkdev.as.me/call-audit
🤖 Your company needs AI experts, to figure out and build new products? We have a new experts division just for that: mkdev.me
📧 Need Cloud and DevOps experts and architects? Read out to us at [e-mail] or schedule a call at mkdev.me
💌 Subscribe to mkdev dispatch and get a chance to get personalized mug: mkdev.me/dispatch
🎙️ Check out our bi-weekly podcast DevOps Accents, directly from mkdev co-founders: mkdev.me/podcast
#aws #googlecloud #gcp

[@1____-____1]

The whole point of these cloud providers is to obfuscate the true cost. And they make implementing the components simple, so the last thing on anyone's mind is cost and ease of use. They also don't have the costs of a solution or an implementation of a product. You should be able to select every component of a product and get the price. If you have a service that runs on EKS and uses S3 and Redshift, secrets manager, and a lambda function to rotate keys, blah, blah, blah... I should be able to plug all of that into one cost calculator.