@LeoCDamascena @hugaomarques @JeffQuesado @ocodista Vou responder amanhã pq precisaria de ~15 tweets pra explicar que

- custo é uma dimensão ampla; em todos os casos que vi em 8 anos de Serverless, computação eh um dos menores custos

- cold start representa <1% em todos os clientes em produção desde 2015

- Serverless != Lambda @LeoCDamascena @hugaomarques @JeffQuesado @ocodista A dificuldade deste tipo de conversa em várias profissões de TI é que a tomada de decisão não vai envolver algo tão simples como requisições por segundo

A dificuldade está em “custo de oportunidade”

Pra dev, eh mais “barato” recriar S3
Pra ops, eh mais “barato” recrie RDS etc.

At last, I can break out the news that...

Powertools for AWS Lambda is now an official AWS team!!!!!!!

This secures:

🤩 Long-term project sustainability
🤩 Feature parity across languages
🔥 New home
🚀 Plan beyond Lambda

1/

#aws #serverless https://t.co/NyuGi1DJlkdocs.powertools.aws.dev
The public beta went out at re:Invent 2019 as a humble demo for Tracer, Logger, Metrics

Powertools for AWS Lambda (Python) started with Observability

We wanted to help customers implement AWS Well-Architected Serverless Lens practices in < 5 minutes

2/

@productiveprog @paulswail @theburningmonk I sincerely don’t even know where to begin to list all caveats with single table, but to ask one question first:

Why do you need a single table design?

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

GraphQL solves the data access issue

hey @darkosubotica thanks a lot for helping promote Lambda Powertools. It made my day, and possibly @NMoutschen and @Tom_McC too

We haven't promoted the latest utilities but ICYMI, check the Utilities section with the latest good practices

/1
awslabs.github.io/aws-lambda-pow… Parameters utility by @NMoutschen helps you fetch one or more parameters from:

👉Parameter Store
👉Secrets Manager
👉DynamoDB
👉Your own provider (S3, AppConfig, etc.)

Docs: awslabs.github.io/aws-lambda-pow…

LOL quite the contrary... having anxiety and being anxious are not the same.

Comments like these tend to share simplistic solutions. It actually makes matters worse and don’t help the mental illness discussion we should be having

Go see a professional (therapist), not a coach

https://twitter.com/iam_preethi/status/1309730256861818882

Other unhelpful comments to those with anxiety, general anxiety disorder, etc

Why are you so organised?
Why cant you finish one thing before jumping to the next?
You seem to take a lot on yourself, try relaxing a bit
Why do you always have a plan B, and C for everything?

[Serverless Python Tip with SAM]

If you're trying to share code as well as common libraries across a few functions within your project - Check this out

You can use a local path to include requirements.txt, and additional local packages you want 👇

github.com/aws-samples/aw… However, by only using Lambda Layers it'll break your autocompletion when developing locally incl. tests

For VS Code, you can extend PYTHONPATH by simply adding a `.env` file at the root of your project

👇 /2

github.com/aws-samples/aw…

🔥 AWS Lambda Powertools for Python is now GA 🔥

We're now GA with four utilities

🌟Core: Tracer, Logger, and Metrics
🌟Bring your own middleware

Core contributors: @Tom_McC @NMoutschen

More details in this 🧵

#serverless #aws #python
github.com/awslabs/aws-la… Last year I was fortunate enough to speak at re:Invent about Serverless Architectural Patterns and Best Practices

That preceded the work we've been doing with the AWS Well-Architected Serverless Lens since 201, however there was to it than patterns..

As we experience this overexposure of information from all sources at nearly all times, remember that it’s okay to take a break from technology.

It’s okay to take therapy, to read a book that isn’t related to work, to do anything manual, etc

Cultivate your mental health This isn’t normal times, it’s no longer “working from home” but more like survival while trying to work.

I spent roughly 25 hours just speaking to people this week, and I too feel unproductive - It’s okay to feel that, but we need to talk more openly about this

Do I know anyone with experience maintaining and automating common OSS tasks?

I could use some help/ideas on

- Changelog(s) for dependabot (as a lib maintainer)
- Automating release notes, stale issues/PRs
- Good practices for contribution guides, docs, etc

#oss For those following this thread, here's some interesting findings

Collection of super useful apps for GitHub projects: probot.github.io/apps/

Collection of awesome OSS readmes: github.com/matiassingers/…

Scheduling team reminders: help.github.com/en/github/sett…

Long overdue but made remaining updates to the Serverless Airline before we start working on exciting improvements

List of Twitch episodes along with their PRs: github.com/aws-samples/aw…

All back-ends documented including decision log: github.com/aws-samples/aw…

/1 Front-end architecture, conventions, design choices, and auto-generated docs for documented code

github.com/aws-samples/aw…

Moved to 1-click deployment due to new enhancements: github.com/aws-samples/aw…

Upcoming improvements (Ops, resilience, etc): github.com/aws-samples/aw… /2

This year I was blessed with the opportunity to speak 6x at reinvent - My first breakout session after 6yrs tenure.

I also had to immense pleasure to meet people I look up to in person, including proper quality time with some Serverless Heroes.

Here’s a summary if you missed ARC307-R Serverless Architectural Patterns & Best Practices covered:

1. REST
2. GraphQL
3. Webhooks
4. Fan-out
5. Streaming
6. “Strangler” for migration

Each patterns showed as POC, and changed after each slide as we applied best practices using Well-Architected pillars

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

aws.amazon.com/blogs/aws/safe…

Our very own and savvy developer develop are @jbesw !!

#serverlessSthlm James walking us the complexity of microservices integration over time as an intro to how events can help us make that process easier.

#serverlessSthlm

Next up is @TServerless speaking about the full development lifecycle of a Serverless App!

#serverlessSthlm Efi reinforcing the principle to Integ/E2E test against cloud resources.

Now we learn from the one and only @orysegal about Serverless Security.

Get ready @NMoutschen @mavi888uy @rchrdbyd and @jbesw

#serverlessSthlm He starts by reminding everyone about Shared Responsibility Model, and how that differs when you adopt Serverless

#serverlessSthlm

Last talk of the day! @thewizardlucas #Vaaiiiii!

Super awesome to have another Brazilian speaker — Live coding on FP. Another Brazilian talking about Lambda — Everyone’s asking - “Are we brothers?”

Cc @simalexan

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”

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