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.
A study conducted in 2017 estimated that there would be around 2.93 million apps in Apple’s App Store by the end of that year. The study also estimated that this number would grow to over 5 million by 2020. So why are we even mentioning this right now? Because more applications today are relying on serverless architectures than you think. Even some big brands have started to go serverless. Don’t believe us? Take a look at these real-world serverless examples. You might be surprised to find out which giants are relying on this technology.
Slack is a cloud-based platform that provides teams with tools they can use to collaborate. It has become a popular business solution for small companies. The Slack Bots the app relies on are some of the platform’s most defining features. And there’s one bot, in particular, that is a serverless application: Slack’s marbot. This bot sends notifications from AWS to development and operations teams by way of Slack. The bot integrates with cloud applications such as:
Lambda Expressions plays an essential part in this process. And if you want to know more about Lambda Expressions, you should check out this blog post. It will help you understand why Lambda is so important when building serverless apps.
Amazon has become a giant, and in more than one way. From sporting goods to scented candles, it sells everything buyers could ever want. And let’s not forget about its hold on the audiobook market. As of 2018, its Audible service was the largest seller of narrated books. The service had sold more than 400,000 titles. Now Amazon is looking to expand its hold on the audiobook with Amazon Polly. Amazon Polly is one of Amazon’s first AI services. This service turns text into realistic speech. And it relies on Amazon Web Services’ CloudFormation to do so. The process of how Amazon Polly accomplishes this task is somewhat complex. That said, you can take a look at how it works on Amazon’s official blog.
Technically speaking, this real-world example is pretty general. There are, after all, several message-driven apps. And there’s nothing that says that every single message-driven app uses serverless technology. But many message-driven apps rely on serverless tech, and for a good reason. Message-driven applications typically have to collect several pieces of information at once. Advertisement platforms are a great example in this case. When you click on an advertisement, the platform must redirect you to a new web page. But the platform must also simultaneously record the fact that you clicked on that advertisement. Why? Because the platform has to charge the advertiser for each click in a PPC campaign. This simultaneous collection of information is what serverless technology excels at. The technology processes multiple messages in parallel.
There are several more real-world serverless examples we could provide. But there are way too many for us to list them all here. That’s how popular serverless technology has become. In any case, feel free to browse our site for other examples. We’ve discussed other companies’ use of serverless technologies in the past (Netflix, Coca-Cola, etc.).
And if you’ve used serverless technology before, let us know what your experience was in the comments section below. We’d love to get another perspective on the tech.
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.
End-to-end observability and real-time error tracking for AWS applications.