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.
API Gateway is a serverless service by AWS to expose cloud services through private or public HTTPs endpoints.
It is used by many serverless teams to connect frontend applications to backend systems in a secure, scalable and seamless way. API Gateway integrates with Lambda, DynamoDB, S3 and a variety of other AWS services.
The main issue with API Gateway, so far, was its cost. At $3.50 per million requests, it can be more expensive than Lambda itself. Paying more to an HTTP endpoint than to the actual computing service makes little sense.
API Gateway comes with a bunch of additional features that are awesome, but add cost to the service: API Key management, API access plans, fine-grained authentication, throttling, etc.
What we observe in reality is that a large portion of software projects only use API Gateway as an HTTP proxy to connect a request to a backend service (e.g. a Lambda function).
To facilitate the adoption of API Gateway, AWS decided to provide a version of it working solely as an HTTP API proxy with +70% price reduction: $1.00 per million invocations.
Despite being in beta, teams that perhaps would fall for another solution (such as an Application Load Balancer) for cost savings can now start using the traditional API Gateway REST API, and later migrate to the cheaper HTTP API when generally available.
We’ve published a thorough guide on the new HTTP APIs feature and how to creating and managing a cost-effective API serverless infrastructure.
API Gateway HTTP APIs preview is available in the following AWS regions: N. Virginia (us-east-1), Ohio (us-east-2), N. California (us-west-1), Oregon (us-west-2), Ireland (eu-west-1), Frankfurt (eu-central-1), Tokyo (ap-northeast-1), and Sydney (ap-southeast-2).
Today we are announcing a new, updated pricing model and the end of free tier for Dashbird.
In this article, we’re covering 4 tips for AWS Lambda optimization for production. Covering error handling, memory provisioning, monitoring, performance, and more.
In this article we’ll go through the ins and outs of AWS Lambda pricing model, how it works, what additional charges you might be looking at and what’s in the fine print.
Dashbird was born out of our own need for an enhanced serverless debugging and monitoring tool, and we take pride in being developers.
Dashbird gives us a simple and easy to use tool to have peace of mind and know that all of our Serverless functions are running correctly. We are instantly aware now if there’s a problem. We love the fact that we have enough information in the Slack notification itself to take appropriate action immediately and know exactly where the issue occurred.
Thanks to Dashbird the time to discover the occurrence of an issue reduced from 2-4 hours to a matter of seconds or minutes. It also means that hundreds of dollars are saved every month.
Great onboarding: it takes just a couple of minutes to connect an AWS account to an organization in Dashbird. The UI is clean and gives a good overview of what is happening with the Lambdas and API Gateways in the account.
I mean, it is just extremely time-saving. It’s so efficient! I don’t think it’s an exaggeration or dramatic to say that Dashbird has been a lifesaver for us.
Dashbird provides an easier interface to monitor and debug problems with our Lambdas. Relevant logs are simple to find and view. Dashbird’s support has been good, and they take product suggestions with grace.
Great UI. Easy to navigate through CloudWatch logs. Simple setup.
Dashbird helped us refine the size of our Lambdas, resulting in significantly reduced costs. We have Dashbird alert us in seconds via email when any of our functions behaves abnormally. Their app immediately makes the cause and severity of errors obvious.