has ya’ll considered localstack at all? or more broadly, is it really true that serverless first organizations really don’t muck about with local development, and rely on cloud-side resources? (I’ve yet to find any serverless dev who spouts “pure” local development - ie. with localstack or similar)

I reckon most in here are in the process of migrating from sls to sst where you can have the best of both worlds. Cloud resources access from a locally running lambda

I understand

sst

has a really nitfy approach where I can still get live-updates to my deployed lambda as I edit (which I still want to figure out how its done)

My experience of localstack and sls offline was one of frustration, nothing quite works as you hope and you get no confidence that when deployed for real things like permissions are going to be right

yeah.. was similar for us. re-*wiring SDKs, only for local development always felt a little blah - let alone hoping that your lambda events could even be targeted by the localstack (like dynamodb streams, or sns subscriptions etc) a lot of user-land plugins to hope support you

My perspective probably represents an extreme so take it with a grain of salt. Serverless is a brand new type of architecture so a lot of things we're used to should look a lot different. Localstack seems like trying to recreate the old way of doing things (running services locally) and it's a cat and mouse game for them to keep up with AWS's changes. Serverless native development should be done as much in the cloud as possible to mirror a production environment. There are some cases where this is impractical (which is why SST live debugging exists or a local dynamodb instance) but even in these situations we want to run as little as possible on the developer's machine. SST takes a lot of effort to make sure the code executing locally thinks it's in AWS. This model steps us closer to closing the gap on "works on my machine but not in prod"

"I understand 

sst

 has a really nitfy approach..." - exactly that. Your code runs locally but accesses and is accessed by real resources inside of AWS. Live reloading and step through debugging in a real cloud env are suddenly possible

“_SST takes a lot of effort to make sure the code executing locally thinks it’s in AWS_”

lol, better than what i was looking at

I think the easiest way to convince somebody is to create a simple SST application tied to an API Gateway. Stick a break point in there, call it from Postman, watch the breakpoint get hit

lol I mean, I haven’t convinced my team to switch yet - need to show them a bit more

that has been the "ah ha" moment for my team

but that is a huge selling point, we’re already doing most of what sst does, but with home-brewed solutions

Appreciate you spreading the word 🙌🏽

and how often have you done that, deployed and then it doesn't work because service A isn't authorised to talk to service B?

yeah, it’s usually IAM that people cite as why “pulling the cloud down onto your machine sucks”

yeah

aws-cdk (and sst) really go all the way, and blend the two - premium

The permissioning thing is so real. I love the new workflow where I can just debug permissions progressively entirelly locally

not to mention static analysis becomes trivial

I’m waiting around for the day that I can ditch my huge noisy macbook, cos my vscode is running in a browser against a dev box in the cloud. I feel like the toolkit is coming together now

That's the one thing I'll never give up. I'm on an overpowered desktop with Linux

Haha blasphemy - used to have a gaming PC but now living the truly serverless way with Stadia & GFN

I’ve had advisors and such tell me to go fully remote - I work in a regulated industry so it does make some sense.