Operations | Monitoring | ITSM | DevOps | Cloud

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.

No matter what’s driving your move to an AWS or Azure cloud, two things are true. One, you don’t want to under-provision, which could create performance and availability issues. And two, you don’t want to overpay, because no one ever wants to do that. One of the key decisions you must make is which Amazon EC2 or Microsoft Azure virtual machine instance configuration you need. It’s a scoping exercise, but several factors make this easier said than done.

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 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.

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.