2) Multi-datacenter -- I want to deploy to two places at least so my risk goes down
The lack of database and/or storage would be a big showstopper. It would mean that if I want build anything with state, I need to store it in another service, which costs money to move data out of. Even a very basic key store would better than nothing. You could actually build one pretty easily on top of Postgres or even SQLLite (although you'd need one per customer w/ SQLLite).
https://www.lite-engine.com/blog/api_queries.html
Edit: To the downvoters: self promotion is allowed on this site, and in fact encouraged!
1. Loop detection does seem harder to implement but I'll definitely look into it (if the api service is used, it would be trivial to implement)
2. but multi-datacenter has almost been implemented (you can select from different service providers, regions or a combinations of each - and the functions would scale accordingly).
As for a database/key store...would integrating with database solutions from other cloud providers be of some consideration? (from GC / AWS / Azure?).
Keep in mind that all users would have access to environment variables (across projects/functions etc.) by default.
I would also like to have something I could point at a docker api which would manage the end to end lifecycle of a function. Building it into a container, exposing itself over an API for management, telling it when it should run and of course running it on my docker machine(s). This idea I don't imagine is appealing to your audience however.
> I would also like to have something I could point at a docker api which would manage the end to end lifecycle of a function. Building it into a container, exposing itself over an API for management, telling it when it should run and of course running it on my docker machine(s).
Could you please go into a bit more detail? I don't understand what you are trying to do. (or it's use case)
However...it does have some current caveats (can only run on a single machine, and definitely not something you'd want to run in production).
But it's (with more features obviously) something I've considered for v1 as an enterprise/maybe OSS feature (as most enterprises would love to host it themselves/behind their firewall/on their private cloud)
I'm currently working on a side project (which if successful can easily be a product in itself) to create a service that would be the Digital Ocean of FaaS (lots of talk - I understand).
What would be the core features that devs/users/managers are looking for? (something you downright expect for v1 that would compel you to put the service to use for development/production)
Currently some of the items top of my list (in no particular order) are:
* API development (like AWS's APIG)
* Support for more languages by default
* Ability for users to a custom defined language easily
* Creation of an opinionated framework / workflow for FaaS development (you don't need to do this if you don't want to...but FaaS first apps would be done better/easier this way)
* Rewriting common products (Wordpress, Ghost, Jekyll etc.) for to be served via FaaS.
Things I don't want to work on (or would prefer to not jump into):
* Storage service (S3 alternatives)
* Databases (there are so many out there...building a cloud is hard, building a database is even more so)
Who do I feel would pay for this?
* Front end & Mobile devs who don't want to complicate a backend
* Mobile devs who don't want to complicate a backend
* Enterprises maybe?