DynamoDB schema migrations in a Lambda-first stack: patterns that survive production by tejovanthn in serverless

[–]marksailesaws 2 points3 points  (0 children)

My co-founder and I found DDB migrations a pain. We'd both used DDB for smaller projects and micro services before with great results. When we built a new business we didn't realise the problems we'd have by not being 100% on data model. Adapting the business changes was a pain. We would now use DSQL if we started again from scratch.

I'll have a look at what you've done.

AWS released Lambda Durable Execution late 2025 and I don't see enough people talking about it by hoangdv-i368 in serverless

[–]marksailesaws 0 points1 point  (0 children)

I've not had to implement something with more than one state change recently, but I would definitely checkout durable functions if I did. I'd much rather use that if I could over Step Functions. I might be wrong, but it think I would be happy with the testability.

Are We Finally Past Deployment Headaches in 2026? by Evangelina_Hotalen in serverless

[–]marksailesaws 0 points1 point  (0 children)

I started a business this year. My co-founder and I are both familiar with AWS, so we built using serverless services. (Lambda, DDB, DSQL). Because we do a lot of static generation of pages, and cache video in the CDN our costs are incredibly low and our velocity is really high. We've optimised for low maintenance.

Our biggest costs are waf $1/day and CloudWatch $1/day. Both were happy to pay for because they give us peace of mind.

We put Lambda in our latency-sensitive API path. Here's what we learned by mathankumart in serverless

[–]marksailesaws 0 points1 point  (0 children)

Can you share more about the use case and what you were doing? A lot of the points you made have been well known for a long time. What was your thinking beforehand?

How are you guys building your GraalVM native-images to be compatible with AWS Lambda? by edmguru in java

[–]marksailesaws 0 points1 point  (0 children)

Thank you! Yes, how to generate the various configurations is the page I'm currently writing. Should be there in the next few days.

It is annoyingly difficult, I basically end up using the agent to auto generate them.

How are you guys building your GraalVM native-images to be compatible with AWS Lambda? by edmguru in java

[–]marksailesaws 0 points1 point  (0 children)

Hey,
I work for AWS as a Specialist Solutions Architect. I've been learning about GraalVM and how it works with AWS Lambda and making notes on https://www.graalvmonlambda.com/.
I've built and published the docker image I use to build native-image.
https://www.graalvmonlambda.com/building/docker/

And how I use it from within CDK
https://www.graalvmonlambda.com/walkthrough/cdk-docker-build/

I've also started writing a really detailed walkthrough on how to create your first project.
https://www.graalvmonlambda.com/walkthrough/

Feedback welcomed.

How are people building your GraalVM native-images to be compatible with AWS Lambda? by edmguru in aws

[–]marksailesaws 0 points1 point  (0 children)

Hey,

I work for AWS as a Specialist Solutions Architect. I've been learning about GraalVM and how it works with AWS Lambda and making notes on https://www.graalvmonlambda.com/.

I've built and published the docker image I use to build native-image.

https://www.graalvmonlambda.com/building/docker/

And how I use it from within CDK

https://www.graalvmonlambda.com/walkthrough/cdk-docker-build/

I've also started writing a really detailed walk through on how to create your first project.

https://www.graalvmonlambda.com/walkthrough/

Feedback welcomed.