We recently wrote about the reasons why serverless apps fail and explored some ideas to make architectures more resilient and scalable. Some of these architectural designs can become expensive if we don’t consider the financial impacts of architectural decisions. With proper care and consideration to this aspect, it is possible to achieve the same value in terms of scalability and resiliency while keeping costs at a manageable level.

Looking for an end to end visibility on your Serverless Application made with Azure resources? This article is for you. Consider there is a transaction between the Azure Services. With the existing solutions offered by Azure, you cannot have the visibility on the transaction as well as the stages in the transactions. Here comes the Business Activity Monitoring in Serverless360. With a simple scenario, we will see how to use Business Activity monitoring and track business data.

There is an interesting discussion going on around how Serverless is more of a spectrum rather than a binary choice. The move towards the Serverless-end of the cloud spectrum builds upon a decades-old trend, which is why Serverless is here to stay.

Azure Service Bus messages may contain sensitive business information. This sensitive information should be accessible only to the intended receivers of the message. This information must be protected from the attackers when the messages are in transit and at rest. This blog will brief you how Azure handles the default encryption of data at rest and how we can use our own keys to encrypt the Service Bus data at transit.

The use of Serverless execution models is expanding extremely rapidly and cloud providers are continuing to enhance their platforms. Per Flexera’s “State of the Cloud” report: Leading this trend for the last two years, Amazon has released a few features that address AWS Lambdas’ pain points and make them a more feasible choice for large scale deployments consisting of numerous applications.

We’ve been monitoring 100,000’s of serverless backend components for 2+ 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.

We are happy to present the Serverless360 release update for Q1 of 2020. The first massive release for the Q1 in February 2020 included the most awaited Business Activity Monitoring along with dashboards for Logic App and Function App and few other useful enhancements. It is so encouraging to find Business Activity Monitoring meeting requirements of customers to attain end-to-end message visibility on their business workflow.

The Azure Functions team has yet again joined us for another monthly live webcast by staying remote and safe. In this live webcast, along with Jeff Hollan, Anirudh Garg and Sonia from Engineering team joined us to give a picture on the latest happenings in Azure Functions space. Without any further delay, let us jump in as there are tons of update are awaiting.

Dashbird, a platform for serverless application monitoring, has raised $2.1 million in a seed round. The investment was led by Paladin Capital Group, with participation from Passion Capital, Icebreaker.vc and Lemonade Stand.

We recently wrote about why serverless applications fail and how to design resilient architectures. Being able to detect early-stage failure indicators can be invaluable. With proper monitoring, developers move from waiting for the system to crash and adopt a more proactive attitude in managing resource allocation and architecture design to avoid bottlenecks and performance degradation.