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.

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.

In a typical enterprise, there would be multiple Azure subscriptions managed across various tenants. Each tenant would have multiple subscriptions for respective environments. This blog focuses on managing the multiple Azure Subscriptions with Serverless360. Let us take a simple scenario to have a better understanding of how Serverless360 overcome the challenges faced in the Azure portal with the help of Composite Application.

Azure Serverless Applications are indeed powerful and super-efficient in delivering the right solution sooner to the market. However, the Azure portal is just not enough to meet the operational and support requirements of the Serverless Application. Organizations cannot afford to invest time and effort in skilled Azure resources in proving support.

Azure Functions has recently released its new version “Azure Functions 3.0” and it is generally available now. This blog is all about the upgraded version and how far it is scaled up from the previous versions. Any business architecture will involve Azure Functions, this need provokes the necessity of upgradation in such resources.

The experts from Azure Functions team has yet again joined us for the monthly webcast. Given the unprecedented time, this webcast happened a bit unusual where the folks joined from their home rather from Channel 9 studio and which made this webcast even more unique and exciting. In this session, Jeff Hollan, Eduardo and Alex Karcher have joined to give us the picture of the latest happenings in the Azure Functions space.

This blog will brief on the distinction between Azure Service Bus Topics and Azure Event Grid. First let us see a short introduction of what these Azure services are, before getting deeper into their distinctions. It is important to note the difference between services that deliver an event and services that deliver a message. Service Bus topics handles messages whereas Azure Event Grid handles events.

Azure Service Bus is a brokered messaging service offered by Azure that can be used to decouple the various applications forming the business integration solving the business problem. The Applications transfer messages between them to share the data between them. The messages can be in XML, JSON or simple text format.

There are two types of queuing mechanisms supported by Azure. Storage Queues are part of the Azure Storage infrastructure, feature a simple REST-based GET/PUT/PEEK interface, providing reliable, persistent messaging within and between services. Service Bus Queues are part of a broader Azure messaging infrastructure that supports queuing as well as publish/subscribe mechanism, and more advanced integration patterns.