Good point. And it’s likely that the vast world of polling processes are not going to be recast with event-driven replacements for some time. But, this is on Airtable; they should have addressed this ages ago. So today …
Should they constrain new innovation by making it guesswork for customers if a new and innovative use of event automation will be (a) sustainable, and (b) affordable?
In my view, the past should not compromise Airtable’s ability to create competitive distance and the customer’s inability to assess or predict whether or not their innovations will fit a given budget.
Another dimension of this is in-platform and out-of-platform calls. Amazon is very clever about data movement across its network boundaries with far more expensive rates when data leaves their data center. They make it almost zero cost to perform compute operations inside the AWS domain. Other PaaS providers (like Airtable) should embrace this approach or force all of us to subsidize the bandwidth costs associated with the few customers who move data into and out of the Airtable realm.
Indeed, but this is a metric that few - even experienced developers - can easily predict. As such, it’s like building a leasing model where you are charged based on the number of times the engine’s cylinders actually fire. We don’t do that to consumers because they would never be able to relate to this metric. Instead, we use something relatable - like miles.