jayair

Yeah it's a big change.

Workspace support is being worked on, it was half-implemented before, so we are taking a proper pass at it now.

For switching between sessions, can you tell me about your workflow from before? Because a tab can hold a session from any project. Are you saying that opening up a tab is too heavy of an action?

GitHub issues though has been a problem from us, we deal with a ton of noise/spam.

Oh wrong Adam, our Adam cofounded Statmuse https://x.com/adamdotdev

Yeah it's something we need to get better at.

I'm biased but for local development, I prefer to emulate the least amount of AWS services. You don't have to deal with any gotchas while going to prod.

Some background, with SST we connect your local environment to the services deployed to AWS and just run the Lambda functions locally: https://docs.sst.dev/live-lambda-development

If you are looking for a guide on building full-stack apps on AWS, check out: https://serverless-stack.com/guide.html

It covers a small subset of AWS services but it is very comprehensive in what it covers.

Yeah I'm going to send this to the Netlify support. Thanks for the details!

Wow that antivirus warning on the docs is super weird. It's just a very simple docs site deployed through Netlify. Can you send me a screenshot of what you are seeing? I'll need to dig into it: jay@serverless-stack.com

Yeah it's a bit of a legacy name from our guide at Serverless-Stack.com but we've got some changes planned!

Sorry to hear that you've had some bad experiences with SST. Recently we shipped some updates to fix the CPU issues with apps that have a large number of functions. The missing breakpoints I think is related as well.

That said though, we often work with teams in our Slack to get their setup working well. If you haven't, I'd recommend popping in and posting about it. Or just send me an email: jay@serverless-stack.com and we'll figure it out.

If you are using CDK then check out SST: https://github.com/serverless-stack/serverless-stack

It's based on CDK and has a great local development environment for Lambda. It allows you to set breakpoints and test it locally: https://serverless-stack.com/examples/how-to-debug-lambda-fu...

Yup it's meant to be a starting point for projects of all sizes. We built our own stuff using it as well. Feel free to reach out if you have any questions. Or join us on Slack: https://launchpass.com/serverless-stack

Good luck!

Yeah exactly, it builds on parts of serverless-nextjs.

It's pretty much to run it on serverless infrastructure as opposed to on containers. And to take advantage of Lambda@Edge.

For a more full-featured serverless setup, you can check out SST: https://github.com/serverless-stack/serverless-stack

It runs on your AWS account and it comes with a local development environment (https://docs.serverless-stack.com/live-lambda-development) as well.

Hi HN, SST (https://github.com/serverless-stack/serverless-stack) is an open source framework we built for serverless. It allows you to debug your Lambda functions locally while invoking them remotely (https://docs.serverless-stack.com/live-lambda-development).

In this example, we show how to set breakpoints through VS Code and inspect a Lambda function. Let me know if you have any questions about how this works.

Wow I really appreciate that! Thank you!

Thanks!

We had to change the build process of Lambdas to support deploying a mock version of the function. And we need to add a new command that deployed the debug stack.

Here's how it works internally — https://docs.serverless-stack.com/live-lambda-development

Your existing CDK app should work with SST. The main difference is that SST deploys per stage (or environment). This allows you to do `sst start` that goes to one environment and `sst deploy --stage prod` that goes to another.

We love esbuild and we use it internally for SST https://github.com/serverless-stack/serverless-stack.

The work Evan does is seriously impressive.

Ah I see what you are saying. Not that this approach is an anti-pattern compared to other serverless setups. But that serverless in general is an anti pattern.

I can see where you are coming from. What we are doing with SST does seem very complicated just to get a good local development setup.

That's not good! We want to add support to GCP and Azure as well.

You could watch our repo — https://github.com/serverless-stack/serverless-stack. Our Twitter account could work also — https://twitter.com/ServerlesStack

Thanks! We'd love to cover as many cases as possible. Feel free to open an issue and we'll add it to our roadmap!

That's cool to hear! I'd love to see that implementation if possible.

LocalStack is a good initiative but in practice it ends up being slow. As a result, we see people using it for writing tests instead of local development.

Using these Docker images works well to emulate the Lambda environment for sure. It just falls short when I want to trigger that through, let's say an SNS topic or an authenticated API that my frontend application can connect to.

Yeah, the is exactly the way we felt. While SST's internals might be complicated, from a user's perspective you get a "normal" local development experience.

We personally do, we've been using Lambdas and serverless for the past 4 years. And we've never had to worry about scaling or downtime. We are a small team, so this has a real impact on us.

I'm curious, why do you think this is an anti pattern?

There are a couple things that SST does differently.

- The Live Lambda Development environment that I talked about in the post. That's really the biggest difference. - And instead of CloudFormation YAML, SST uses CDK. So you can use regular programming languages to define your infrastructure.

Yeah it's a little confusing to describe the difference. But what most of the tools currently do is, locally mock a Lambda function execution. You cannot test anything beyond that.

For example, if your Lambda function publishes to a SNS topic that invokes another Lambda function. You can only test this locally my mocking the inputs for the first one, testing that. And repeating it for the second one.

With SST, it deploys this stack to AWS. So when you trigger this workflow, both the Lambda functions get invoked on your local machine. You don't need to mock anything. It is as if they were invoked live.

Yup, we'll be working on it soon. Interestingly, we get more request for Go than Python!

Not sure if you noticed this (https://news.ycombinator.com/item?id=26323888), but it's similar in spirit to the Lambda terminal idea.