single table requires significant engineering effort, onboarding, harder to operate and change, and build your own tooling
@productiveprog@paulswail@theburningmonk Single table patterns are great because it shows the power DynamoDB has - it does not mean you need to put all your data into a single table. You could have a single table per service, or use patterns of a single table in multiple tables
Each patterns showed as POC, and changed after each slide as we applied best practices using Well-Architected pillars
Nov 26, 2019 • 5 tweets • 3 min read
Awesome #aws pre:Invent gifts in the last 24hrs ICYMI
😍Error handling enhanced for Lambda incl max retries, poison pill etc
🤩New Lambda Destinations plus richer metadata for DLQ
🔥New Parallelization Factor for Lambda+Kinesis
🆕Feature-toggle, rollout config w/ AWS AppConfig
Blog posts with more details about these new features.
The new AWS AppConfig and an example of how to integrate with Parameter Store
Finally! @simalexan is on stage talking about Serverless for frontend developers!!
Smashing as always
“I don’t have to wait for for backend/ops engineers to handle Authorization, API, setting up environments”
Sep 5, 2019 • 12 tweets • 4 min read
2 weeks ago I turned 30 years old, and 6 years of AWS — Today, with tears of happiness, I’ve officially got promoted to Principal.
Back in 2012, I had this dream of moving from Ops to Dev, and terrified by the thought of: “Isn’t it too late” /1
I clearly remember my first interview at AWS in 2013 — I felt so overwhelmed with questions that I thought “No way I can pass, people are too smart here”.
To my surprise, I did pass, and first joined as a Cloud Support Engineer (L4) /2