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.
Every couple of days you read about the “next big thing in [enter technology name here]” and it’s hard to tell if there’s anything behind those claims. Yet, I often suffer from a terrible affliction called FOMO – fear of missing out – which makes me spend hours upon hours testing the technology only to find it completely useless and nothing to show for my efforts.
So how can you tell that that new thing you just found out about will stick around for a while? Well, I found that if a technology gets picked up by a big company that usually means it’s here to stay. Using the same logic I’ve put serverless to the test. Here are a few companies that use serverless right now.
You heard that’s right kids, our favorite past time activity provider is using serverless to serve 7 billion video hours to 50 million customers in 60 countries. EVERY. QUARTER. Now while I won’t pretend to understand the intricates of the Netflix infrastructure I will point out that they rely heavily on AWS Lambda to run tasks that would otherwise take up a lot of computing process and even more time to build. The Chief Product Officer at Netflix had a talk at AWS Re-invent where he spoke about the different ways they use serverless in order to provide the best on-demand video streaming service out there (biased alert).
Codepen has been around since 2012 and has quickly become a standard for web developers. People use it to share pieces of code and examples that help newcomers get a jump start in their development career. Right now Codepen servers up to 200 000 requests per hour and while that is impressive, what surprised me is the fact that all their infrastructure is run by a one-man DevOps team. What better way to learn about the wonders of serverless than from the horse’s mouth, to that end, here’s a podcast made by the guys over at codepen.io talking about serverless.
Zalora is one of the biggest fashion stores in Asia employing around 1500 people with a user base of over 20 million users. They have a cool mission statement: “fashion on-demand, 24/7 at your doorstep”. They rely heavily on AWS and Lambda to make sure every customer gets access to the website and apps without worrying about scaling issues. I like to quote their CTO whenever I have the chance as it points out something that most companies will come to realize in the not-so-distant future.
“We outgrew what the server world offered to us and it was the right time for us to switch over to a provider like AWS” – Karthik Subramanian – CTO at Zalora
This came as a surprise to me as I was under the impression that big companies don’t look at the infrastructure cost and think, “how can we cut costs?”. Coca-Cola started migrating to serverless back in 2016 and while they are still in the process of moving everything in the cloud, they are still using traditional servers to service their old technologies but this will only happen until they can “sunset” the older machines. At AWS Re-invent, Coca-Cola’s Michael Connor talks about how a few case studies they made where the result was clear that by using serverless they would cut down costs by 65%.
Nordstrom is an American-based chain of department stores, headquartered in Seattle. The company was founded over a hundred years ago and has been on the innovation side of technologies every since. They started switching from data-driven applications to event-driven applications and have been really pushing the envelope with the creation of an open-source proof-of-concept Serverless architecture retail store called Hello Retail. Rob Gruhl talks to This is My Architecture, an AWS community show about how they are using AWS Lambda to create an event-driven app.
These are just a few of the companies that have already switched server technologies, from traditional servers to serverless infrastructure. Of course, this is by no means a reason to think traditional servers will disappear but having big companies make the jump does point to a not-so-distant future where serverless will be the go-to technology for deploying enterprise applications. We, the folks at Dashbird, are proud to stand next to business giants in our belief that the future is serverless.
In this guide, we’ll talk about common problems developers face with serverless applications on AWS and share some practical strategies to help you monitor and manage your applications more effectively.
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.
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.