Remove limits in favor of pay to play model everywhere
I consider this a bug (defect) as PaaS suggest a pay as you go and you go figure out the hard part of how to make that happen. Queuing and delay may be acceptable, but failure to consumers to me really would generally not be the case unless extreme cases are hit (DDoS or configured limits). There seem to be lots of hard upper bounds at the moment that I would think I could be willing to pay for as a customer to eliminate. It makes Azure Functions unviable in many scenarios today (as the easy option) and I wonder why you have such hard constraints. It is always easy to complain as I presume much thought has gone into these, but the docs outline constraints that make it difficult to suggest this as an option without alternative architectural choices.
Mirko Geffken
shared this idea
1 comment
-
Mirko Geffken
commented
To clarify expanding on my own post. As a customer I might prefer to set a spending limit by PaaS offering. Scale as needed, but when you exceed $? stop this thing. Expanding on that go the google ads route. I care about this PaaS thing on a responsiveness level, so preference responsiveness or I care about this thing responding eventually, obviously the prior costing me a pretty penny and the latter being queued for me.