Live data from Hacker News

Launch HN: Seed (YC W21) – A Fully-Managed CI/CD Pipeline for Serverless

news.ycombinator.com

11–20 of 109 posts

Re: Launch HN: Seed (YC W21) – A Fully-Managed CI/CD Pipeline for Serverless

#12
post #9

I loved reading serverless-stack a couple of years ago; it was really helpful & convinced me to use serverless for a side-project that’s still going (with almost no expenses!). I’m surprised to hear how many separate lambda functions each service in your example had. I understand the need to deploy each service independently... but to have +10 deployments within each service seems crazy to me. Is there a reason each…

Thank you for the kind words about Serverless Stack. Frank and I poured ourselves into creating it. So it makes me really happy when I hear that it ended up being helpful.

On the Lambdas per service front, the express server inside a Lambda function does work. A lot of our customers (and Seed itself) have APIs that need to have lower response times. And individually packaging them using Webpack or esbuild ends being the best way to do it. So you'll split each endpoint into a Lambda.

I just think the build systems shouldn't limit the architectural choices.

Re: Launch HN: Seed (YC W21) – A Fully-Managed CI/CD Pipeline for Serverless

#14
post #9

I loved reading serverless-stack a couple of years ago; it was really helpful & convinced me to use serverless for a side-project that’s still going (with almost no expenses!). I’m surprised to hear how many separate lambda functions each service in your example had. I understand the need to deploy each service independently... but to have +10 deployments within each service seems crazy to me. Is there a reason each…

Frank here from Seed. Just wanted to add that when you have a monolithic Lambda, multiple routes would share a CloudWatch log group, metric, and share a common node in x-ray. On the flip side, the advantage of having separate Lambda functions handling each route lets you leverage other AWS services better.

Re: Launch HN: Seed (YC W21) – A Fully-Managed CI/CD Pipeline for Serverless

#15
Weird to see "folks" everywhere in the text. Why not "people"? Or "developers"?

I'm sure it's not on purpose, but it made me think about Social Justice language war: https://newdiscourses.com/tftw-folks/

(I even had to switch to my anonymous HN account to post this.)

I would prefer to think about this (very cool!) startup instead.

Re: Launch HN: Seed (YC W21) – A Fully-Managed CI/CD Pipeline for Serverless

#16
I have achieved this with AWS Cloudformation/SAM, a template.yml and a makefile. Polyglot too, a mix of Python backend and JS backend across multiple functions.

I’m trying to think of how a service would help me here. However I do think this is a frontier-space where there is a lot of room for improvement. Looks polished though, I’ll take it for a spin on a hobby project soon.

Re: Launch HN: Seed (YC W21) – A Fully-Managed CI/CD Pipeline for Serverless

#17
post #10

Well done, and thanks for Serverless Stack! Awesome tutorial! I completed it and it was excellent, and a lot of fun. The only thing I would say is that a section on public user uploads would be amazing (e.g. avatars) as the perms and CDK stuff is a bit knotty for that (I eventually figured it out but it took a bit of trial and error).

Thank you for the kind words!

That's a good point on the avatars idea. We'll need to create a version of the notes app, where there's a public aspect of it. So maybe being able to publish it.

Re: Launch HN: Seed (YC W21) – A Fully-Managed CI/CD Pipeline for Serverless

#19

Weird to see "folks" everywhere in the text. Why not "people"? Or "developers"? I'm sure it's not on purpose, but it made me think about Social Justice language war: https://newdiscourses.com/tftw-folks/ (I even had to switch to my anonymous HN account to post this.) I would prefer to think about this (very cool!) startup instead.

I noticed this too, I personally prefer the usage of folx
Post reply on HN