Discover and read the best of Twitter Threads about #eventbridge
Most recents (7)
In this #Serverless 101 thread, @edjgeek will give you a high-level overview of various AWS Serverless services through.
He'll cover services like;
➤ #DynamoDB
➤ $SQS
➤ #SNS
➤ #StepFunctions
➤ #EventBridge
➤ #Kinesis
➤ #AWSLambda
➤ #S3
🧵👇 #AWS #CloudComputing
He'll cover services like;
➤ #DynamoDB
➤ $SQS
➤ #SNS
➤ #StepFunctions
➤ #EventBridge
➤ #Kinesis
➤ #AWSLambda
➤ #S3
🧵👇 #AWS #CloudComputing
Serverless 101: Intro
Serverless 101: A series to help you understand what AWS serverless services do. It talks about how to use the services together to build highly scalable applications using event-driven architecture built on serverless.
▶️
👇
Serverless 101: A series to help you understand what AWS serverless services do. It talks about how to use the services together to build highly scalable applications using event-driven architecture built on serverless.
▶️
👇
Serverless 101: Amazon SQS
A high-level overview of SQS. SQS is a fully managed message queuing service that makes it easy to decouple and scale microservices, distributed systems, and serverless apps.
▶️
👇
A high-level overview of SQS. SQS is a fully managed message queuing service that makes it easy to decouple and scale microservices, distributed systems, and serverless apps.
▶️
👇
Great thoughts & opinions in 👇 and in Jeremy's bit.ly/3prk4OA
To me, @awscloud should focus on providing a #Serverless adoption & application experience (AX) than simply improving DX by mixing a bit of UX and getting nowhere. 🧵
1/
To me, @awscloud should focus on providing a #Serverless adoption & application experience (AX) than simply improving DX by mixing a bit of UX and getting nowhere. 🧵
1/
As a cloud prvoider and with the scale of services and adoption, for #AWS, it's difficult to play the balancing act.
Too few service cause frustration and too many services lead to confusion. Adding more new services is not always a healthy situation.
2/
Too few service cause frustration and too many services lead to confusion. Adding more new services is not always a healthy situation.
2/
As Jeremy mentioned, the maturity of the existing services is crucial. He also beautifully described what a DX is in the cloud world. It's not about adding some UX and calling it DX.
3/
3/
Everyone got so excited about Graviton2 Lambda functions & Step Functions AWS-SDK integration yesterday that you might have missed this one about triggering Lambda functions from SQS queues in *different* accounts. This is important, a short 🧵 #serverless aws.amazon.com/about-aws/what…
Having multiple AWS accounts to handle different parts of your application (from both a lifecycle and service perspective) isn't just good practice, it's also AWS recommended. 👍 2/9
This is because AWS account separation is the best isolation model for security, scalability, regional controls, service limit management, billing 👈, and much more. 3/9
Very cool #reInvent session by @sliedigaws about building out distributed applications using different #EventBridge patterns. Let's recap this quickly to see how we can use them to build out our #serverless apps. 🧵
The "single-bus, single-account" pattern is a super simple way to get started, especially if you have a small team. Create logical service boundaries and use a single event bus to decouple the services. This is one of my favorite ways to prototype #serverless applications.
The "single-bus, multi-account" pattern is my go-to for larger apps, and works great for multi-team orgs w/ service-level ownership reqs. Create a *global* event bus, grant access to service accounts for putEvents, and forward events to service-owned buses for rules & routing. 👍
1/ Everyone understands the power of APIs. But what happens when a Database gets an API? #AWS #Redshift got one recently and it opens up plenty of new use cases. A thread 👇
2/ Until September 2020, Redshift required clients to use JDBC/ODBC based connections through the drivers it provided. But that changed when the Data API was introduced. With Data API, you can now fire SQL queries through a simple HTTPS endpoint docs.aws.amazon.com/redshift/lates…
3/ You can use the familiar IAM based auth and this API is integrated in AWS SDKs. Which means you can now programmatically run SQL queries just like invoking any AWS API. You simply invoke the “execute-statement” API by providing the SQL query and get an execution id in response
Three newsworthy updates to evb-cli just reached the internet😲! Details in thread in asc order of goodness👇
evb-cli is a tool that integrates with #EventBridge Schema Registry letting developers build complex event patterns in seconds.
💾npmjs.com/package/@mhlab…
evb-cli is a tool that integrates with #EventBridge Schema Registry letting developers build complex event patterns in seconds.
💾npmjs.com/package/@mhlab…
Update 1:
Pass the CLI the path to your template to get the option to inject the generated pattern where you want it. Works for both JSON and YAML and for both AWS::Serverless::Function and AWS::Events::Rule resources 👌
Update 2:
Full support for numeric matches 🧮
Pass the CLI the path to your template to get the option to inject the generated pattern where you want it. Works for both JSON and YAML and for both AWS::Serverless::Function and AWS::Events::Rule resources 👌
Update 2:
Full support for numeric matches 🧮
Update 3:
Typos happen when working fast. You can now undo any mistake whilst building patterns instead of restarting the tool 🎇
Typos happen when working fast. You can now undo any mistake whilst building patterns instead of restarting the tool 🎇
I *LOVE* what the @awscloud #EventBridge team is doing for #serverless, and this new Schema Registry is an amazing next step! Here are my initial thoughts on this... aws.amazon.com/blogs/compute/…
EventBridge _should_ become the glue that ties together all your cloud services (eventually w/ two-way message bindings). This means that the number of event types (don't forget SaaS partners) is going to increase exponentially...
Security best-practices will evolve to prefer multiple event buses so you'll have fine-grained access control across SaaS vendors, AWS service events, and custom messaging. The cognitive load to understand all those nuances, limitations, and event structures is overwhelming...
