jayair

13 ms·

61.
by jayair 6y ago
The interesting thing is that it lets you develop against your real infrastructure. This speeds up your iteration cycle drastically when compared to the other serverless tools. But I do feel your pain, building a CI/CD for serverless i
62.
by jayair 6y ago
The big difference is that Chalice (from what I remember) runs a local server where you test your functions and once you are ready, you'll deploy it to AWS. This deploys it to AWS first, and when a function gets invoked remotely, strea
63.
by jayair 6y ago
Yeah this is a framework that's completely for local development. We have a separate service that's a CI/CD pipeline for serverless apps. We use a SaaS model there — https://seed.run . It supports SST out of the bo
64.
by jayair 6y ago
I partly agree that it's weird that it takes something complicated to solve local development. That said, we've explored a wide range of options over the past few years and the local emulation route can be really hard to setup and
65.
by jayair 6y ago
Yup, we have a separate SaaS product for teams, a CI/CD pipeline for deploying serverless apps. It supports SST and Serverless Framework. https://seed.run
66.
by jayair 6y ago
Appreciate the support Pal! All your feedback has been really helpful.
67.
by jayair 6y ago
So the `sst start` command fires up a local environment but it doesn't deploy your functions. Instead it'll run it locally when it gets invoked. But when you `sst deploy` it, we'll package your functions. To do this we use es
68.
by jayair 6y ago
Appreciate it! Yeah we really want to fix this, given how much time we spend working on it!
69.
by jayair 6y ago
Thank you! Glad to hear that it's been working well.
70.
by jayair 6y ago
We'll be looking at Python in the coming weeks, currently it's JS and TS only. But the way this works locally (for Node) is that you do an npm install just as you would and it executes your application locally. The packaging part
71.
by jayair 6y ago
Yeah the internals of the `sst start` command are a little complicated. But it only needs to setup it up initially, from that point on it simply connects to the WebSocket API. SST is open source and runs on your AWS account. We don't c
72.
Launch HN: SST (YC W21) – A live development environment for AWS Lambda
165 points by jayair 6y ago|88 comments
73.
by jayair 6y ago
Yeah that sounds familiar. We went through a lot of that. Feel free to get in touch if you need any help jay@seed.run
74.
by jayair 6y ago
For some reason that repo is internally set to private, I'll check and see why that is.
75.
by jayair 6y ago
It's similar in speed on a per function basis, but the main difference is that we figure out which ones need to be updated and do them all concurrently. Plus handle any failures and retry them.
76.
by jayair 6y ago
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...
77.
by jayair 6y ago
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 abou
78.
by jayair 6y ago
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 tha
79.
by jayair 6y ago
While you can deploy static websites as a part of your stack on Serverless Framework and CDK; Seed isn't doing anything specific for it. Under this scenario, the static site is hosted on the user's AWS account. Is that what you me
80.
by jayair 6y ago
Currently, there's isn't a way to do it directly on Seed. It can be triggered using a git push. But we've got a CLI in the works, and that should let you control when you want to trigger a deploy.
81.
by jayair 6y ago
We've built custom infrastructure just for Serverless Framework and CDK. So it's a lot faster (thanks to the incremental deploys), reliable (we handle failures and retries by connecting directly to your CloudFormation events), and
82.
by jayair 6y ago
I talked a little bit about it here: https://news.ycombinator.com/item?id=25838954 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.ru
83.
by jayair 6y ago
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
84.
by jayair 6y ago
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, thi
85.
by jayair 6y ago
Thanks! We do but it's a bit further down the roadmap.
86.
by jayair 6y ago
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 s
87.
by jayair 6y ago
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:
88.
by jayair 6y ago
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, deployin
89.
by jayair 6y ago
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
90.
by jayair 6y ago
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-serve

More ›