Launching Our Knowledge Base

It’s been a long time in the making but after months of pushing it on the back burner, we are finally ready to release our newest project.

Serverless technology has evolved at a thrilling pace. As a result of the rapid growth and expansion of this whole new space, many developers felt overwhelmed. Our goal, with this project, is to provide clarity and information to the serverless community by tackling topics that span from the most mundane and simple definitions to some advanced serverless topics.

Sure, most answers can be figured out by running a quick Google search but reliable information is just as common as the unreliable ones, so getting the correct answer can be difficult at times.

We felt like we needed to develop a better solution. A central place where developers and serverless enthusiasts can get any information on the latest trends, technologies and architecture design without spending hours digging through the colossal amount of information that’s available online.

This is how we ended up creating the Knowledge Base. It’s open and licensed under Creative Commons.

Knowledge Base covers everything related to web and mobile development. From basic concepts to advanced architectural patterns. Especially related to serverless technologies. We’re writing about reliable cloud services that can enable successful implementations, as well.

It’s still a work in progress and we’ll try to expand it as we move forward with more tutorials and tips that should help both the new serverless developers that are just getting started as well as the more seasoned developers that have been working with serverless since day 1.

knowledgebase

Suggestions and contributions from the development community are more than welcome. Please create an issue if you have anything to share!

Read our blog

5 Common Amazon SQS Issues

As with all services on AWS, issues can crop up while using SQS because it’s not always obvious what every service can and cannot do. But fear not, for this article aims to help you solve the most common ones as quickly as possible. Ready to fix your queues? Then let’s dive in!

5 Common Step Function Issues

Here you will find the most common issues when working with Step Functions, especially when starting with the service.

6 Common DynamoDB Issues

It’s expected that developers face many of the same issues when starting their NoSQL journey with DynamoDB. This article might clear things up a bit.

More articles

Made by developers for developers

Dashbird was born out of our own need for an enhanced serverless debugging and monitoring tool, and we take pride in being developers.

What our customers say

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.