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
ARN stands for Amazon Resource Name. It’s a unique identifier for resources in the AWS Cloud: an server instance, a database instance, a queue buffer, etc.
The ARN can be useful when developers need to refer to a resource in an documentation, for example. Or when it’s necessary to request help from the AWS support team.
The ARN has the following format:[^1]
arn:partition:service:region:account-id:resource-type:resource-id
The resource-type is optional. When it’s omitted, the ARN is presented as:
resource-type
arn:partition:service:region:account-id:resource-id
Each ARN always starts with arn and is composed of five additional terms (listed below), separated by comma :. Another variation is a slash to separate the resource-type from the resource-id:
arn
:
resource-id
arn:partition:service:region:account-id:resource-type/resource-id
By default, the partition value is always aws. There are special cases in China of infrastructure locations where AWS depends on partners. In this case, it may show aws-cn.
aws
aws-cn
Identified the AWS service to which the resource belongs. It could be lambda, ec2, rds, dynamodb, or any other service.
lambda
ec2
rds
dynamodb
Indicates in which AWS Region the resource is deployed. It could be us-east-1 or eu-west-2.
us-east-1
eu-west-2
For a complete list of AWS Regions and their ARN identifiers, please check the AWS documentation.
Also read our guide about the AWS Global Infrastructure to understand what is a Region and an Availability Zone in AWS.
Identifies the AWS account that owns the resource. This is particularly useful in internal documentations for teams that use multiple accounts. It is a good practice to have one account for development and testing purposes, and a separate account for production usage.
The value of resource-type and resource-id varies according to the service.
In DynamoDB[^1], for example, a table has the following format: table/{table-name}. A Table stream has the following format: table/{table-name}/stream/{YYYY-MM-DDThh:mm:ss.ddd} (e.g. table/my-db-table/stream/2020-01-15T19:00:27.055).
table/{table-name}
table/{table-name}/stream/{YYYY-MM-DDThh:mm:ss.ddd}
table/my-db-table/stream/2020-01-15T19:00:27.055
A Lambda function will have the following resource-type and resource-id: function:{function-name}.
function:{function-name}
[^1]: AWS Documentation about ARN
[^2]: Check our introductory guide on DynamoDB.
No results found