Monitoring platform for keeping systems up and running at all times.
Full stack visibility across the entire stack.
Detect and resolve any incident in record time.
Conform to industry best practices.
Dashbird continuously monitors and analyses your serverless applications to ensure reliability, cost and performance optimisation and alignment with the Well Architected Framework.
What defines a serverless system, main characteristics and how it operates
What are the types of serverless systems for computing, storage, queue processing, etc.
What are the challenges of serverless infrastructures and how to overcome them?
How systems can be reliable and the importance to cloud applications
What is a scalable system and how to handle increasing loads
Making systems easy to operate, manage and evolve
Learn the three basic concepts to build scalable and maintainable applications on serverless backends
The pros and cons of each architecture and insights to choose the best option for your projects
Battle-tested serverless patterns to make sure your cloud architecture is ready to production use
Strategies to compose functions into flexible, scalable and maintainable systems
Achieving loosely-coupled architectures with the asynchronous messaging pattern
Using message queues to manage task processing asynchronously
Asynchronous message and task processing with Pub/Sub
A software pattern to control workflows and state transitions on complex processes
The strategy and practical considerations about AWS physical infrastructure
How cloud resources are identified across the AWS stack
What makes up a Lambda function?
What is AWS Lambda and how it works
Suitable use cases and advantages of using AWS Lambda
How much AWS Lambda costs, pricing model structure and how to save money on Lambda workloads
Learn the main pros/cons of AWS Lambda, and how to solve the FaaS development challenges
Main aspects of the Lambda architecture that impact application development
Quick guide for Lambda applications in Nodejs, Python, Ruby, Java, Go, C# / .NET
Different ways of invoking a Lambda function and integrating to other services
Building fault-tolerant serverless functions with AWS Lambda
Understand how Lambda scales and deals with concurrency
How to use Provisioned Concurrency to reduce function latency and improve overall performance
What are Lambda Layers and how to use them
What are cold starts, why they happen and what to do about them
Understand the Lambda retry mechanism and how functions should be designed
Managing AWS Lambda versions and aliases
How to best allocate resources and improve Lambda performance
What is DynamoDB, how it works and the main concepts of its data model
How much DynamoDB costs and its different pricing models
Query and Scan operations and how to access data on DynamoDB
Alternative indexing methods for flexible data access patterns
How to organize information and leverage DynamoDB features for advanced ways of accessing data
Different models for throughput capacity allocation and optimization in DynamoDB
Comparing NoSQL databases: DynamoDB and Mongo
Comparing managed database services: DynamoDB vs. Mongo Atlas
How does an API gateway work and what are some of the most common usecases
Learn what are the benefits or drawbacks of using APIGateway
Picking the correct one API Gateway service provider can be difficult
Types of possible errors in an AWS Lambda function and how to handle them
Best practices for what to log in an AWS Lambda function
How to log objects and classes from the Lambda application code
Program a proactive alerting system to stay on top of the serverless stack
Below are some of the main characteristics that makes EventBridge an appealing service, as well as the benefits it can bring to cloud applications.
Event Bridge is, in many cases, one of the best ways to implement an asynchronous messaging pattern for a cloud system.
EventBridge delivers not only a loose-coupled architecture, but also enables:
These are the three essential characteristics of an asynchronous pattern implementation.
Event schemas and the Schema Registry makes it a lot easier to manage large scale applications running on top of EventBridge.
These two features allows developers to discover and track tempaltes for event messages used by the system. This provides a centralized communication channel for different developers (or teams), responsible for different components, to account for and work upon eachothers’ services.
There are no servers to provision or maintain when using Event Bridge. As usual, AWS provides services quotas1 and SLAs in which developers can rely upon without worrying if the underlying infrastructure components will work when needed.
This is especially benefitial if resilience is one of the main goals when applying an asynchronous architecture. By relying on a serverless offering by AWS, the development team can abstract away worries about infrastructure uptime, performance and other issues.
First, the Event Bridge does not work based on topics, like the Pub/Sub mechanism. There is one single bus for a whole set of different and unrelated types of events.
While it is possible to create multiple buses, it is not required. Even though it’s possible to work with unrelated messages in a Pub/Sub architecture, it becomes cumbersome and difficult to manage as the number and complexity of message types grow.
Internally to AWS, an EventBridge bus can seamslessly connect to Lambda functions, EC2 instances, Kinesis streams, CloudWatch logs, Containers, State Functions, Batch jobs and many more services.
EventBridge also comes with a set of SaaS partner services that can automatically push events to buses, such as Segment, SugarCRM, Zendesk and more.
When it comes to flexibility and interconnectivity, this rich integration set puts EventBridge ahead of other services such as SQS (queues) or SNS (Pub/Sub topics).
No results found