Sometimes, the data you want to analyze lives in AWS S3 buckets by default. If that’s the case for the data you need to work with, good on you: You can easily ingest it into an analytics tool that integrates with S3. But what if you have a data source — such as logs generated by applications running in a Kubernetes cluster — that isn’t stored natively in S3? Can you manage and analyze that data in a cost-efficient, scalable way? The answer is yes, you can.

We’ve been monitoring 100,000’s of serverless backend components for 3+ years at Dashbird. In our experience, Serverless infrastructure failures boil down to: These isolated faults become causes of failure due to dependencies in our cloud architectures (ref. Difference of Fault vs. Failure). If a serverless Lambda function relies on a database that is under stress, the entire API may start returning 5XX errors.

Another generic error message from our favorite FaaS provider AWS Lambda. And again, there are multiple reasons why this issue could arise. Let’s first look at the basics of AWS Lambda to get a better intuition for when things go wrong later. Lambda is an asynchronous event-based service at heart.

While Spot by Netapp allows organizations to reliably and affordably run production environments on spot instances, operation teams always want to be alerted about any events of interest that occur in their environment. Over the last 5 years, Spot by NetApp customers have been using our existing notification mechanism and have shared excellent feedback for various enhancements and new capabilities.

We’ve reviewed the year that was, how business big and small had to fast forward their digital transformation to accommodate remote work and keep their businesses in business. Some IT leaders have said because of the pandemic, they were able to expedite digitalization and digital transformation within their organizations. Efforts previously envisioned to take months or years were moved forward and achieved in a matter of weeks.

At Taloflow we recently launched a way for companies migrating from AWS/GCP/Azure to 3rd party object storage providers like Storj to receive an objective TCO analysis of all the switching and storing costs associated. But what exactly is object storage - and how does it compare to block storage? For both, we will cover the technical description, benefits, and application use-cases.

As a cloud cost intelligence platform, we spend nearly every day talking to companies about their cloud cost — and there’s something we’ve noticed — people don’t generally have the warm and fuzzies for their cloud cost management tools. You know, the ones that have been around for a while, that you use to build reports about your cloud spend? We won’t refer to them by name. These popular tools have really given the whole category a bit of a bad rap.