Like any other creation in progress or in the making, serverless applications, need to be tested and monitored. How else would you know if what you’ve created is providing desired results? Before putting your “newborn child” out into the world, you must make sure that it’s ready for the world. Software or even hardware of any sort will first be tested before it goes to mass production, and the same goes for your serverless applications.
I’m going to be biased in this post and it’s going to be ok because all the information you’re about to see are 100% correct and fair towards both services.
Smarter people than myself, once said that you should do things you don’t like first so that you can enjoy the things you’re doing later. Nobody wants cold starts. They’re annoying, and we continuously feel an itching sensation in our brains because of them. The serverless world would be a much better place to work in if they weren’t there.
Mikk and the rest of the dev team at Dashbird have been working overtime this past month, in an effort to rehaul the user experience in the app based on the feedback we are constantly getting. We believe in having an honest and open, two-way street when it comes to communication so I advise each and every one of you to either write us an email via support@dashbird.io or to join our slack channel.
The phrase “better safe than sorry” gets thrown around whenever people talk about monitoring or getting observability into your AWS resources but the truth is that you can’t sit around and wait until a problem arises, you need to proactively look for opportunities to improve your application in order to stay one step ahead of the competition.
FaaS services such as AWS Lambda take care of many security aspects - networking, firewall, OS updates, etc. Make no mistake, though: application-level security is still fully on our hands! Do we have all the information needed to secure our serverless apps? Enters critical logging!
This past couple of month were a bit hectic and there’s a good reason behind that. We’ve set out to create a better experience for our users, and it’s exactly what we did! Besides making a lot of quality-of-life changes, we’ve introduced new features that we think, will speed up the speed at which you’ll debug your applications and give you a whole new perspective on all things AWS Lambda.
It’s the celebration time of the year! Dashbird is now an official Amazon Web Services (AWS) Advanced Technology Partner (APN). Our team has demonstrated that we can build a strong, secure and reliable AWS-based business that can benefit Amazon Web Services users. The new partner status is recognition of Dashbird ability to help companies to better monitor and troubleshoot their Lambdas by providing state of the art solution for serverless observability.
Today we’ll talk more about the cost tracking for serverless architecture. Following the cost of serverless architecture utilization it might give you insights on how and what should you change or adapt to, to be able to reduce the cost. After all, we’re all always trying to improve our performances in every field while keeping the costs to a minimum (if possible).
This post is going to be a tad different and longer than what you are used to but I promise, it’s going to be an interesting one. We are going to build a serverless React + GraphQL Web app with Aws amplify and AppSync.
