My eyes have recently been opened to PlayFab's pricing model. It's something I really just sort of skimmed over as I've been learning how to integrate PlayFab into an app, but I thought it would be a very good to learn before progressing any further. The pricing for Cloud Script executions got me thinking.
When I first learned of Cloud Script, my initial thought was "This is awesome! I can use Cloud Script for metrics-based bookkeeping." I mean, the examples of using Cloud script on PlayFab's website are short, clear, and concise. They don't take much memory and likely have very fast processing time. It would be perfect for my needs.
And it does work for my needs, but having recently put two and two together, I learned that EACH Cloud Script execution has a "minimum billable memory size and execution time [of] 128MB and 100ms, respectively". That has a potential of adding up very quickly depending on the individual implementation of Cloud Script in an application.
I cannot help but wonder what the original intention of the Cloud Script functionality was? For instance, using it for metrics type stuff with a 200 byte (if that) script clearly does not seem to fit the intended usage. It just seems that execution of small scripts wasn't the main focus of this really cool feature.