All-in-one serverless DevOps platform.
Full-stack visibility across the entire stack.
Detect and resolve incidents 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
As mentioned in the Main Benefits and Characteristics page, EventBridge is commonly a very good service for implementing asynchronous messaging across a system in order to decouple independent services.
Instead of having one service calling another directly, EventBridge can be used to receive event messages and handle routing to the appropriate services. To learn more, check the page about serverless functions composition strategies.
Processes that may go through multiple status changes during its lifecycle in systems that need to respond to changes can benefit from EventBridge.
A logistics service may need to trigger different actions depending on what is the status of a package. When it leaves the distribution center and starts heading to the final destination, the system may need to send an alert through e-mail or SMS to the recipient, for example.
An e-commerce backend system may need to handle confirmation messages to the buyer once payment is confirmed, or the package is shipped, or it might need to respond to status changes from the logistics department to keep the inventory, financials, and customer service departments in sync.
Different departments within a company or actions might need to be triggered depending on the status of a customer support ticket, for instance.
In all these cases, EventBridge can be used as a central location to receive all status changes (events) and route to the services that need to be aware of those changes in order to appropriately respond to them.
Related to the above examples (Tracking and responding to status changes), companies that have to deal with multiple systems and keep them in sync can also benefit from EventBridge. All changes from one system can be pushed to the event bus and later processes by the adjacent systems that rely on the information.
The disadvantage here is that the synchronization process will be eventually consistent, as updates on one side won’t reflect immediately on the other systems.
Since EventBridge connects to external third-party services, such as SugarCRM1, it’s possible to create workflow automation processes connected to customer service and sales activities. The system may trigger the financial department to issue an invoice, for example, whenever a sale is closed.
EventBridge is very flexible and its vast integration set makes it even easier to adapt the service to a wide variety of use cases. The examples above are meant to serve as an introduction and for illustration purposes, not to exhaust all possibilities, which wouldn’t be feasible in this article.
No results found
End-to-end observability and real-time error tracking for AWS applications.