81–90 of 109 posts
How does seed compare to aws cdk pipelines https://aws.amazon.com/blogs/developer/cdk-pipelines-continu... I know if I go the route of cdk pipelines I will need to implement my CI/CD pipeline on my own using cdk. I want to know what are the other advantages of seed.
But the big one for CDK is that it's faster and basically free on Seed.
Feel free to get in touch if you want more details! jay@seed.run
What is the benefit of this over let's say gitlab ci?
I build my first lambda 4 years ago and it was great: no servers, no complicated tools. Just one function which I upload and it works. The amount of tooling which exists now is just daunting. At this point, is it still worth it if the technology is so complex that people are building the whole SaaS for managing it? PS YC is still bullish on selling shovels I see.
I think that's fair. When we started back in 2016 with Lambda, it was similar to how you describe it. Now we've got a ton of companies that just use Lambda. So you can imagine a team for 50 developers, working on 40 or so separate services, with 500 or so Lambda functions. It can be hard manage the tooling for all of this internally.
If you use a few sparingly, great.
When you are at a team of 50 working on 40 separate services with 500 Lambda's or so I don't see how you are better off than writing a self contained service that's deployed as a single artifact i.e microservice.
You get the advantage of all related code grouped together, easy to instrument / test / run on any platform. All the advantages of a mono repo but at a service level, non of the orchestration or special tools to deal with 500 disparate lambdas and wiring up event sources / sinks.
Thank you for ur service. I just registered. I previously used aws cicd tools to do this. They integrated well for my simple use case. Can i trigger a deploy daily?
But we've got a CLI in the works, and that should let you control when you want to trigger a deploy.
Nah, my enterprise customers are mostly on Azure. But, yeah functions are useful sometimes.
This looks great. If you added support for easy/integrated static site hosting, this would be a compelling alternative to Vercel and Netlify. Any plans for that?
Under this scenario, the static site is hosted on the user's AWS account. Is that what you mean when you are thinking about an alternative?
We've talked about this internally, so I'm curious to hear about your use case.
Earlier quoted context omitted.
This is getting out of hand. Are there "monolithic" and "micro" functions now?
That made me chuckle. But to be fair, in this case "monolithic" function is just a way to describe this pattern of moving your entire app (express in this case), inside a Lambda function. When Lambda started to become popular, this was the most common way to migrate to it. Just move your monolithic app to a function, hence "monolithic" functions.