These guys have done an outstanding job, definitely take a look. It's an indispensable tool.
Launch HN: Seed (YC W21) – A Fully-Managed CI/CD Pipeline for Serverless
21–30 of 109 posts
Re: Launch HN: Seed (YC W21) – A Fully-Managed CI/CD Pipeline for Serverless
#22I 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.
Looking forward to hearing your feedback when you give it a try! I should've clarified in the post, we support all the runtimes, not just Node.
Re: Launch HN: Seed (YC W21) – A Fully-Managed CI/CD Pipeline for Serverless
#23Weird 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
#24I use seed.run and it is absolutely outstanding. The UI is incredibly easy to use and I have so much more confidence in my deployments. These guys have done an outstanding job, definitely take a look. It's an indispensable tool.
Re: Launch HN: Seed (YC W21) – A Fully-Managed CI/CD Pipeline for Serverless
#25I use seed.run and it is absolutely outstanding. The UI is incredibly easy to use and I have so much more confidence in my deployments. These guys have done an outstanding job, definitely take a look. It's an indispensable tool.
Wow thank you! Really appreciate your support!
Re: Launch HN: Seed (YC W21) – A Fully-Managed CI/CD Pipeline for Serverless
#26Weird 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
#27Of course 'it depends', but roughly speaking?
Re: Launch HN: Seed (YC W21) – A Fully-Managed CI/CD Pipeline for Serverless
#28I 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…
Obviously this can expand the blast radius of any vulnerability and tends to encourage rougher grained privilege grants.
Re: Launch HN: Seed (YC W21) – A Fully-Managed CI/CD Pipeline for Serverless
#29Looks great. For someone who's not taken the plunge into Serverless yet, how would the costs compare to the more traditional options of hosting an app? i.e. a Rails/React app on Heroku Of course 'it depends', but roughly speaking?
But here are the caveats. If your usage patterns are 24/7 and very predictable. You can design your infrastructure to be cheaper than the Lambda.
However for most other cases, including us at Seed (we use serverless extensively). It's so much more cheaper that we wouldn't do it any other way.
If you have a hobby project, it'll be in the free tier.
Some more details here — https://serverless-stack.com/chapters/why-create-serverless-...
Re: Launch HN: Seed (YC W21) – A Fully-Managed CI/CD Pipeline for Serverless
#30Looks great. For someone who's not taken the plunge into Serverless yet, how would the costs compare to the more traditional options of hosting an app? i.e. a Rails/React app on Heroku Of course 'it depends', but roughly speaking?