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
An API Gateways Provides flexibility to use completely independent protocols allowing your microservices to communicate among themselves with ease. They allow developers to access the functionality of a subset of architecture in many different ways, without ever exposing the endpoints publicly. It doesn’t matter if you are using microservices or serverless architecture or a public API, API Gateways have a lot of benefits to offer.
Since API gateway sits between your front end applications and the microservices it will act as a security barrier making sure your sensitive API Endpoints are not exposed. It also protects your API from malicious attack vectors such as DoS attacks, SQL injections, and other several other similar attacks that take advantage of the API’s vulnerabilities.
Some API clients can even integrate with data stores that handle session information like Redis which is designed to be accessed by trusted clients inside the environment. Without and API gateway the Redis instance would be exposed directly to the client which would present some security risks.
Your API gateway will manage concerns like rate limiting, user access control, token authorization, scaling among others and help you reducing complexity and allowing your API to focus on the task at hand.
This type of decoupling creates an unprecedented advantage since your actual API doesn’t have to process or format the response in any way. Routing is done by the API gateway, formating the response is done by the API gateway and even cache can be handled by the same API Gateway.
Some API gateways come out of the box with certain monitoring or analytics tools that help the developers debug and create infrastructures that can scale gracefully. Since this is not common to most API Gateway service providers there are several third-party monitoring and observability solutions that can help you figure out what’s going on behind the scenes.
Dashbird.io is a perfect example. It connects directly to the AWS API Gateway and collects valuable information like errors, execution time and invocation details.
There are lots of reasons for use and API Gateway but there are certain drawbacks that you should consider.
There’s a learning curve when it comes to architecting applications high availability applications at scale especially since the API gateway is going to be the single point on of entry between the front end and the APIs it will also act as a single point of failure.
Configuring your application and API to interact via an API Gateway will require some more orchestration which will add a level of difficulty for the developers.
Performance degradation is a concern due to the multitude of scenarios that the API Gateway will handle and can impact the speed and reliability of your application.
No results found
End-to-end observability and real-time error tracking for AWS applications.