Ask HN: Recommendations for choosing a serverless framework
Want it to be as less maintainable as possible in addition to low-cost, autoscaling. To be honest, not bothered about vendor lock-in, to reduce dev hours & cost. This is also an opportunity to learn about serverless architecture of development and so not doing it as a monolith.
Few reqmts: 1) Need to interact with a database, which could also be serverless (say aurora or firestoredb). Should have a reliable workflow for database migrations. 2) Should have an excellent offline, local development workflow. Should not expect me to talk to cloud for local development. 3) Should be easy to integrate with gitlab/github to do continous deployment 4) Should have support for multiple deployment environments (Production, Staging, Demo) 5) Should have well defined ways for .env files, ENV variables for reading sensitive info (API Keys)
Some contenders that I see (with first opinions on shallow googling) are: 1) serverless - Seem to be the oldest. Seems trusted by AWS 2) openfaas - Seems good. No vendor lockin. But not supported by either AWS or GCP officially. Not too keen on vmware cloud. 3) KNative - Still seems immature. By the lethargic pace in which GCP is moving (especially related to Golang support) I am not too keen on this. Not 1.0 yet I believe. 4) AWS Fargate - Seems like the best solution. No need to break every HTTP handler into an unit of deployment. Integrates with AWS ecosystem (cloud watch, vpc ...)
Bonus points for frameworks that support: 1) automatic code structure gen, given a swagger YAML(openapi 3.0) 2) Integrations for logging, tracing etc. with standard tools (like elasticsearch, cloudwatch, stackdriver, prometheus, etc).
So, Here I am seeking the opinions/experiences/comments of HN crowd about serverless frameworks / tools you used. Thanks.