There is so much more to running a cloud system than running a function - monitoring the function (billing, errors, throughput, latency), scaling the function, moving data between two functions, storing data, signaling a function, upgrading a function, downgrading a function, upgrading the stored data, authorizing the function to run, upgrading and downgrading stored data and functions while taking customer traffic with zero downtime without data loss.

"Backend-as-a-service" businesses need to check all of those boxes.

I'm going to decompress part of your comment here:

- scaling the function

This is where we've invested most of our effort. We're envisioning a load test demo soon.

- monitoring the function (billing, errors, throughput, latency)

This is something which we will need to invest more in. Great feedback here. We don't have much in the way of monitoring yet, but everything is there and we just need to expose it to the users.

- moving data between two functions, storing data

Traditional solutions like Redis and Postgres seem like a good solution here. You can't host them on Coherence yet, but it's something that we're working on.

- signaling a function, upgrading a function, downgrading a function

Versioning is particularly interesting here. A lot of time we've thought of these functions as ephemeral.

Send me an email (bryan at coherenceapi . com) I'm really interested to talk more about the use cases you're envisioning.