dalssoft
commented
1 year ago Things we have to consider:
-
Which serverless framework we will use? Probable Serverless Framework, right?
-
It should be integrated with the CLI
-
Is it integrated with the Herbs2Rest and Herbs2GraphQL? Are they a dependency?
-
Is it possible to use Herbs2Serverless without generating any file (all on-the-fly)?
-
How the extra metadata will be used? (e.g. the metadata for Herbs2Rest and Herbs2GraphQL)
-
How it would handle other abstraction like permissions, resources, packaging, deploy, multiple endpoints and more?
These are some questions that I have in mind. I think that we should discuss it more deeply.
Is your feature request related to a problem? Please describe. As a support platform for microservices and with the growing demand for serverless applications, it would be important for herbs to support the framework. Facilitating the configuration of routes and deploys, mainly on AWS.
Additional context We already have a draft here: https://github.com/herbsjs/todolist-on-herbs/pull/123 And an issue about it here: https://github.com/herbsjs/herbs-cli/issues/75