Christ, all you need is a function to stick in there. A "boilerplate" for serverless is an oxymoron.
Show HN: Serverless boilerplate to get started quickly
11–19 of 19 posts
Re: Show HN: Serverless boilerplate to get started quickly
#12Re: Show HN: Serverless boilerplate to get started quickly
#13OT: Who has experiences with serverless and which providers/services could yoi recommend?
Re: Show HN: Serverless boilerplate to get started quickly
#14Re: Show HN: Serverless boilerplate to get started quickly
#15Re: Show HN: Serverless boilerplate to get started quickly
#16OT: Who has experiences with serverless and which providers/services could yoi recommend?
I do, and if you are building a large app, I would recommend against using serverless. At least the library, since it has a limit of about 20 endpoints unmodified.
Re: Show HN: Serverless boilerplate to get started quickly
#17isn't this already solved with serverless framework? https://serverless.com/
Re: Show HN: Serverless boilerplate to get started quickly
#18Earlier quoted context omitted.
I do, and if you are building a large app, I would recommend against using serverless. At least the library, since it has a limit of about 20 endpoints unmodified.
I did not know that, could you share a proof to back this statement ?
Actually, now that I think of it, since this is an AWS limitation, it may actually be fine on other providers.
Re: Show HN: Serverless boilerplate to get started quickly
#19Earlier quoted context omitted.
I did not know that, could you share a proof to back this statement ?
Try adding 40 endpoints to one serverless.yml file. You will quickly run over the 200 resource limit for cloudformation. Actually, now that I think of it, since this is an AWS limitation, it may actually be fine on other providers.