4 ms·

cycles can be pretty quick with lambda, definitely faster than launching a container into k8s or ecs. there's good tooling for local execution too

pluto_modadic 2y ago
AWS codepipeline/codebuild still takes a really long time. think 1 minute to notice a commit, 2 minutes to download code, 3-8 minutes to get a codebuild runner, however long your build is, and 30 seconds to update the lambda. Especially when you don't have a good local AWS runner, vs using a HTTP service you can run and live reload on your laptop. deploying to prod in less than 10 seconds, or even /live reloading/ the AWS service would be awesome.
- abadpoli 2y ago
  For fast iteration, our developers build, test and deploy locally using cdk deploy directly into their dev account, no need to wait around for the pipeline to do all those steps. Then when they’re ready, higher environments go through the pipeline. CDK has a new(ish) feature called hotswap that also bypasses CloudFormation and makes deploys faster.
  - chuckadams 2y ago
    The equivalent of hotswap in SAM would be `sam sync --code --watch`. Works in seconds, though I still prefer to test locally as much as possible.
- deleted 2y ago
  [deleted]
nunez 2y ago
I disagree. Pushing your image up to your registry, running `kubectl apply`, waiting for it to schedule your Pod and start your containers and exec'ing into them when shit breaks is WAY faster than zipping up your artifact and any layers that come with it, uploading it into S3, and re-deploying your Lambda functions (and any API Gateway apps associated with them), IMO. When I use Serverless to do this, deploys take up to two minutes, which I sometimes do often because I have no real way of troubleshooting the application within Lambda (definitely necessary if you're using Lambda base images; less necessary if you're rolling your own; likely if you're integrating with API Gateway since documentation on the payloads sent from it is lacking IMO).

pluto_modadic 2y ago

AWS codepipeline/codebuild still takes a really long time. think 1 minute to notice a commit, 2 minutes to download code, 3-8 minutes to get a codebuild runner, however long your build is, and 30 seconds to update the lambda. Especially when you don't have a good local AWS runner, vs using a HTTP service you can run and live reload on your laptop. deploying to prod in less than 10 seconds, or even /live reloading/ the AWS service would be awesome.

abadpoli 2y ago
For fast iteration, our developers build, test and deploy locally using cdk deploy directly into their dev account, no need to wait around for the pipeline to do all those steps. Then when they’re ready, higher environments go through the pipeline. CDK has a new(ish) feature called hotswap that also bypasses CloudFormation and makes deploys faster.
- chuckadams 2y ago
  The equivalent of hotswap in SAM would be `sam sync --code --watch`. Works in seconds, though I still prefer to test locally as much as possible.
deleted 2y ago
[deleted]

nunez 2y ago

I disagree. Pushing your image up to your registry, running `kubectl apply`, waiting for it to schedule your Pod and start your containers and exec'ing into them when shit breaks is WAY faster than zipping up your artifact and any layers that come with it, uploading it into S3, and re-deploying your Lambda functions (and any API Gateway apps associated with them), IMO. When I use Serverless to do this, deploys take up to two minutes, which I sometimes do often because I have no real way of troubleshooting the application within Lambda (definitely necessary if you're using Lambda base images; less necessary if you're rolling your own; likely if you're integrating with API Gateway since documentation on the payloads sent from it is lacking IMO).