Is this faster then using the deploy function command in serverless? Look's very interesting.
Launch HN: Seed (YC W21) – A Fully-Managed CI/CD Pipeline for Serverless
91–100 of 109 posts
Re: Launch HN: Seed (YC W21) – A Fully-Managed CI/CD Pipeline for Serverless
#92I 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 have 50 developers and you can't "manage the tooling for off of this internally" you've got WAY bigger issues.... SMH
Re: Launch HN: Seed (YC W21) – A Fully-Managed CI/CD Pipeline for Serverless
#93Earlier quoted context omitted.
One problem with monolithic functions is that you must grant them a union of all the rights required by every code branch in the monolith. Obviously this can expand the blast radius of any vulnerability and tends to encourage rougher grained privilege grants.
This is getting out of hand. Are there "monolithic" and "micro" functions now?
"microlithic" a micro service which bundles multiple responsibilites.
Re: Launch HN: Seed (YC W21) – A Fully-Managed CI/CD Pipeline for Serverless
#94I 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).
Cloud run is exactly what he described. We use cloud run and it is great.
Re: Launch HN: Seed (YC W21) – A Fully-Managed CI/CD Pipeline for Serverless
#95I 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…
I think you could check Moncc https://docs.moncc.io/ - you can wrap all of the above in a template (provisioning and orchestration) and run locally or on gcp/aws
you can also integrate it with github actions
Re: Launch HN: Seed (YC W21) – A Fully-Managed CI/CD Pipeline for Serverless
#96Looks really neat! I will try it out for my next ~/tmp weekend project. Meanwhile, I noticed that the link to the C# project is broken on this page https://seed.run/docs/adding-dotnet-core-projects . I wanted to try propose the change but I couldn't find the repository on your GitHub.
Re: Launch HN: Seed (YC W21) – A Fully-Managed CI/CD Pipeline for Serverless
#97Earlier quoted context omitted.
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).
Does that use Cloud Run? I haven't tried Google cloud yet because I thought I'd have to learn Kubernetes. I have an aversion to learning Kubernetes because I still can't figure out what problem it's trying to solve. Admittedly, I probably haven't gotten far enough with cloud hosting to know what limitations I'll hit yet though. Some ok answers here: https://stackoverflow.com/questions/55786955/whats-the-value... The…
If you have a simpler implementation then you may have a billion dollar idea on your hands. I look forward to the Show HN!
Re: Launch HN: Seed (YC W21) – A Fully-Managed CI/CD Pipeline for Serverless
#98Earlier quoted context omitted.
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 have 50 developers and you can't "manage the tooling for off of this internally" you've got WAY bigger issues.... SMH
To expand on that, you can build this tooling out internally and many teams do. They just have a team dedicated to building and maintaining something like Seed internally.
What we bring to the table (aside from being more cost effective than staffing for this), is that when we solve an issue for one of our users, it gets solved for everybody else that's using Seed.
In fact, that's how we solved some of the issues around "reliably deploying a large number of serverless services together". One of our users was running up against some errors related to this and we worked with them to figure out the issue and fix it for everybody on Seed.
Re: Launch HN: Seed (YC W21) – A Fully-Managed CI/CD Pipeline for Serverless
#99Earlier quoted context omitted.
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.
I see this as the issue with Lambda's. 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…
I think the complexity aspect is a fair criticism of Lambda.
The way I look at it is that, as a developer, I want all the advantages of serverless (per ms billing, scaling up instantly, scaling down to 0, etc) while not having to worry about the function level nuances of tooling and deploying.
Having struggled with scaling large systems in a past life, I personally lean more towards taking on the burden of tooling instead.
Re: Launch HN: Seed (YC W21) – A Fully-Managed CI/CD Pipeline for Serverless
#100Looks really neat! I will try it out for my next ~/tmp weekend project. Meanwhile, I noticed that the link to the C# project is broken on this page https://seed.run/docs/adding-dotnet-core-projects . I wanted to try propose the change but I couldn't find the repository on your GitHub.
Oops sorry about that. I appreciate you taking the time to try and make a change. Does this link work for you?
https://github.com/seed-run/homepage/edit/master/_docs/addin...