Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

news.ycombinator.com

Post reply on HN
Print view View original

61–70 of 109 posts

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

#61

Post by jayair »

jedberg wrote: post #57
jayair wrote: post #55

Earlier quoted context omitted.

Thank you! They offer something similar but there are a couple of differences. - The big one is the focus on speed, the incremental deploys at a service and Lambda function level ( https://seed.run/blog/speeding-up-serverless-deployments-100... ). - We are also focussed on reliability, so setting up and tearing down environments while handling all the AWS rate-limit errors, or other timing related errors. We do this…

Awesome, thanks for the info! Do you have more info on what you mean by "We do this by connecting directly to CloudFormation"?

Yeah for sure. Previously, we relied on the the Serverless Framework CLI output. But now we directly monitor the CloudFormation events to figure out the root cause of the failure, then decide if we should retry the deployment, and how long to wait to retry.

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

#62

Post by jayair »

leetrout wrote: post #60
jayair wrote: post #22

Earlier quoted context omitted.

Yeah makes sense. Adding SAM support is on our roadmap. 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.

Do you have any rough plans for how you would support SAM? Would you be transforming the YAML in some proprietary way or just calling off to CloudFormation on the users behalf?

Yeah at our core we do CloudFormation deployments. Whether thats through Serverless Framework or CDK (using SST https://github.com/serverless-stack/serverless-stack). So in the case of SAM it would be similar, deploying the CF stack on the users behalf. The deployments process roughly looks like: install dependencies > package functions > generate CF stack > deploy it > monitor progress. We do some optimizations along those steps but thats the gist of how it works.

Hope that helps. Feel free to get in touch if you want to know more jay@seed.run

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

#63

Post by leetrout »

zackmorris wrote: post #59

I wish there was something like this for Docker rather than Lambda functions. I'm new to all of it, but the security groups, route tables, internet gateways and other implementation details of AWS left me feeling overwhelmed and insecure (literally, because roles and permissions are nearly impossible for humans to reason about). AWS also suffers from the syndrome of: if you want to use some of it, you have to learn a…

> docker-compose --some-option-to-make-this-happen-remotely

Some of this exists- you can do remote operations like that with contexts but that doesn't solve the infrastructure issue.

Custom docker images on heroku is closer...

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

#64

Post by jayair »

davecap1 wrote: post #56

How does this compare to something like AWS CodePipeline with CDK ( https://docs.aws.amazon.com/cdk/latest/guide/cdk_pipeline.ht... )?

Most of my post was about Serverless Framework but we support CDK as well (with SST https://github.com/serverless-stack/serverless-stack).

A couple of things that we do for CDK that's different from CodePipeline:

- Setting up environments is really easy, we support PR and branch based workflows out of the box.

- We automatically cache dependencies to speed up builds.

- And we internally use Lambda to deploy CDK apps, which means it's basically free on Seed (https://seed.run/docs/adding-a-cdk-app#pricing-limits)!

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

#65

Post by pongogogo »

zackmorris wrote: post #59

I wish there was something like this for Docker rather than Lambda functions. I'm new to all of it, but the security groups, route tables, internet gateways and other implementation details of AWS left me feeling overwhelmed and insecure (literally, because roles and permissions are nearly impossible for humans to reason about). AWS also suffers from the syndrome of: if you want to use some of it, you have to learn a…

Have you tried cloud run on GCP? It sits in the niche you're describing between a serverless platform and some managed container orchestration platform like kubernetes (GKE or EKS).

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

#66

Post by jayair »

zackmorris wrote: post #59

I wish there was something like this for Docker rather than Lambda functions. I'm new to all of it, but the security groups, route tables, internet gateways and other implementation details of AWS left me feeling overwhelmed and insecure (literally, because roles and permissions are nearly impossible for humans to reason about). AWS also suffers from the syndrome of: if you want to use some of it, you have to learn a…

Yeah I feel your pain in regards to AWS. It was a big reason why we wrote https://serverless-stack.com.

We run some ECS clusters internally and have run into some of the issues you mentioned. We use Seed to deploy them but the speed and reliability bit that I talked about in the post mainly applies to Lambda. So Seed can do the CI/CD part but it can't really help with the issues you mentioned.

Btw, have you tried Fargate?

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

#69

Post by safeerm »

zackmorris wrote: post #59

I wish there was something like this for Docker rather than Lambda functions. I'm new to all of it, but the security groups, route tables, internet gateways and other implementation details of AWS left me feeling overwhelmed and insecure (literally, because roles and permissions are nearly impossible for humans to reason about). AWS also suffers from the syndrome of: if you want to use some of it, you have to learn a…

hey Zack, we have a prototype of this, we would love to have you try out (and anyone else). We just helped a couple customers migrate their Docker code repos from DigitalOcean to AWS and save $2K a month with our template. Gives you a CI/CD pipeline and deploys on ECS/Fargate.

Please reach out safeer [at] tinystacks.com

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

#70

Post by vincentmarle »

becausepc wrote: post #31
vincentmarle wrote: post #19

Earlier quoted context omitted.

I noticed this too, I personally prefer the usage of folx

At least "folks" is a real word. "Folx" is unquestionably the result of the language war: https://newdiscourses.com/tftw-folx/

What's wrong about trying to include other marginalized groups including people of color and trans people?
Post reply on HN