In one of our recent talks with Serkan, our newly announced CEO, he told me about how Thundra actually sparked. He wrote the first Java library of Thundra because there was no monitoring solution for AWS Lambda for Java back in the summer of 2017.
As Stackery’s Ecosystems Manager, a huge part of my work revolves around meeting new people and developing relationships with them for the good of our company. I love this work not only because I’m passionate about people and serverless, but also because it keeps my curiosity muscle strong.
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!
Serverless has, for the last year or so, felt like an easy term to define: code run in a highly managed environment with (almost) no configuration of the underlying computer layer done by your team. Fair enough, but what is is a serverless application?
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.
Werner Vogels, the CTO of Amazon, describes AWS Lambda as the “connective tissue” for your cloud-native application. It’s an apt description, as AWS Lambda functions often connect to many services to transform and move data between them.
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.
I was thrilled to learn that Thundra won Enterprise Management Associates’ prestigious Top 3 award, which identifies top vendors poised to address critical enterprise pain points in serverless adoption.
