Tweet

https://twitter.com/tpschmidt_/status/1422907219612508163

https://twitter.com/tpschmidt_/status/1422179393359814659

https://twitter.com/tpschmidt_/status/1450158394233561093

https://twitter.com/tpschmidt_/status/1448312256165556229

https://twitter.com/tpschmidt_/status/1449030467911569409

https://twitter.com/tpschmidt_/status/1442880455179657219

More from @tpschmidt_

Tobias Schmidt

@tpschmidt_

3 Nov

📚 𝗔𝗪𝗦 𝟭𝘅𝟭 - 𝗦𝗤𝗦

Your fully managed message queue service & a serverless fan's best friend.

From queue types, over visibility timeouts to message groups ↓

𝗧𝗵𝗿𝗲𝗮𝗱 𝗢𝘃𝗲𝗿𝘃𝗶𝗲𝘄 🧵

• Introduction
• Importance of Messaging Systems
• Fundamentals
• Queue Types
• Visibility Timeouts
• Retention Periods
• Limitations

{ 1/22 }

𝗜𝗻𝘁𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝗼𝗻

Believe it or not: SQS was the 𝗳𝗶𝗿𝘀𝘁 publicly launched service by AWS!

Quoting Jeff Bar:
"We launched the Simple Queue Service in 𝗹𝗮𝘁𝗲 𝟮𝟬𝟬𝟰, Amazon S3 in early 2006, and Amazon EC2 later that summer."

jeff-barr.com/2014/08/19/my-…

{ 2/22 }

Read 24 tweets

Tobias Schmidt

@tpschmidt_

27 Oct

📚 AWS 1x1: 𝗪𝗵𝗮𝘁 𝗮𝗿𝗲 𝗟𝗮𝗺𝗯𝗱𝗮 𝘁𝗿𝗶𝗴𝗴𝗲𝗿𝘀?

For a function to execute, an event must occur.
Most know about API Gateway for REST services as an event source.

But a lot more AWS resources can trigger your Lambda ↓

Almost anything that happens within your AWS account is an event.

• writing a record to DynamoDB
• uploading a file to S3
• queuing a message in SQS
• a viewer request to your CloudFront distribution

All of those events can be used to trigger a Lambda function.

{ 1/12 }

There are two different kinds of invocation types: 𝘀𝘆𝗻𝗰𝗵𝗿𝗼𝗻𝗼𝘂𝘀 & 𝗮𝘀𝘆𝗻𝗰𝗵𝗿𝗼𝗻𝗼𝘂𝘀

Synchronous event sources need to wait for your Lambda function to return a response.
Asynchronous don't.

If invoking functions via the SDK, this can be specified!

{ 2/12 }

Read 14 tweets

Tobias Schmidt

@tpschmidt_

26 Oct

📚 Cloud 1x1 - 𝗦𝗲𝗿𝘃𝗲𝗿𝗹𝗲𝘀𝘀 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗮𝗹 𝗣𝗮𝘁𝘁𝗲𝗿𝗻𝘀

You don't need to re-invent the wheel.
You can rely on field-tested patterns.

Let's explore some common ones ↓

𝗣𝗮𝘁𝘁𝗲𝗿𝗻 𝗢𝘃𝗲𝗿𝘃𝗶𝗲𝘄

• Fan-in & Fan-out
• Simple Web Service
• Publish/Subscribe
• Strangler
• Aggregator

{ 1/7 }

𝗙𝗮𝗻-𝗶𝗻 & 𝗙𝗮𝗻-𝗼𝘂𝘁

Common problem: large tasks that are exceeding Lambda's execution time limit
With Fan-out, you're splitting those large tasks into small ones and delegating those to Lambda workers.
Afterward, results are aggregated (= Fan-in).

{ 2/7 }

Read 11 tweets

Tobias Schmidt

@tpschmidt_

25 Oct

𝗟𝗲𝘁'𝘀 𝗯𝗲 𝗵𝗼𝗻𝗲𝘀𝘁: generally, debugging is not a fun task 🤢

Especially for serverless, event-driven & distributed systems.

From Lambda's logging basics to 𝘀𝗮𝘃𝗶𝗻𝗴 𝘁𝗶𝗺𝗲 & 𝗻𝗲𝗿𝘃𝗲𝘀 ↓

Lambda's a serverless technology provided by AWS.
But that 𝗱𝗼𝗲𝘀𝗻'𝘁 𝗺𝗲𝗮𝗻 that there are no servers.

In the background, there are countless micro-containers running on top of the traditional servers.

Where do all the logs of those containers go to?

By default, they will end up in CloudWatch.
Every Lambda will receive its own 𝗹𝗼𝗴 𝗴𝗿𝗼𝘂𝗽.
Like a repository for logs.

Not only that, every micro-container will create a new so-called 𝗹𝗼𝗴 𝘀𝘁𝗿𝗲𝗮𝗺.
Think of it as a text file where logs are written to.

Read 9 tweets

Tobias Schmidt

@tpschmidt_

15 Oct

📚 AWS 1x1 - 𝗟𝗮𝗺𝗯𝗱𝗮 ƛ

The Heart of your Serverless Love Story 🧡

All my learnings & (almost) everything you need to know ↓

𝗧𝗵𝗿𝗲𝗮𝗱 𝗢𝘃𝗲𝗿𝘃𝗶𝗲𝘄

• Introduction
• Cold Starts
• Handler Method
• Runtimes
• Layers
• Security
• Versioning & Aliases
• Provisioned & Reserved Concurrency
• Lambda@Edge
• Pros & Cons
• Observability
• Considerations to make

{ 1/31 }

𝗜𝗻𝘁𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝗼𝗻

AWS released Lambda in late 2014, spreading the buzzword serverless.

With EC2 you didn't have to think about physical servers anymore, but only virtual machines.

With Lambda, there's not even that anymore to maintain.
Just bring your code.

{ 2/31 }

Read 33 tweets

Tobias Schmidt

@tpschmidt_

13 Oct

📚 AWS 1x1 - 𝗗𝘆𝗻𝗮𝗺𝗼𝗗𝗕 💾

My personal holy grail of database solutions & one of AWS' flagship services

An all-embracing mega-thread 🧵↓

𝗧𝗵𝗿𝗲𝗮𝗱 𝗢𝘃𝗲𝗿𝘃𝗶𝗲𝘄

• Introduction
• Provisioned vs On-Demand Capacity
• Basic Concepts
• Keys & Attributes
• Retrieving Items
• Race Conditions
• Expressions
• Indexes
• Streams
• Security
• Backups
• Global Tables
• Observability

{ 1/38 }

𝗜𝗻𝘁𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝗼𝗻

Why should you care about DynamoDB?

It's managed, highly available & scales on-demand with low latencies.

For getting you hooked, at Prime Days 2021 DynamoDB served 𝟴𝟵.𝟮 𝗺𝗶𝗹𝗹𝗶𝗼𝗻 𝗿𝗲𝗾𝘂𝗲𝘀𝘁𝘀/𝘀𝗲𝗰𝗼𝗻𝗱 at its peak.

{ 2/38 }

Read 40 tweets

Share this page!

Tobias Schmidt

Try unrolling a thread yourself!

More from @tpschmidt_

Tobias Schmidt

Tobias Schmidt

Tobias Schmidt

Tobias Schmidt

Tobias Schmidt

Tobias Schmidt

Did Thread Reader help you today?

Like this author's thread?