Tips, Expertise, Articles and Advice from the Pro's for Your Website or Blog to Succeed
One of the previous blogs covered some of the concepts behind how Azure Event Hubs supports multiple protocols for data exchange. In this blog, we will see it in action using an example. With the help of a sample app, you will see how to combine real-time data ingestion component with a Serverless processing layer.
The sample application has the following components:
Azure Event Hubs is a streaming platform and event ingestion service that can receive and process millions of events per second. In this blog, we are going to cover one of the security aspects related to Azure Event Hubs.
Shared Access Signature (SAS) is a commonly used authentication mechanism for Azure Event Hubs which can be used to enforce granular control over the type of access you want to grant - it works by configuring rules on Event Hubs resources (namespace or topic). However, it is recommended that you use Azure AD credentials (over SAS) whenever possible since it provides similar capabilities without the need to manage SAS tokens or worry about revoking a compromised SAS.
Microsoft has announced new Azure SDKs that meet updated Azure SDK API standards. The new libraries Microsoft has released are for Azure Storage, Azure Cosmos DB, Azure Key Vault, and Azure Event Hubs. Microsoft has been working on a new set of API standards that will apply across Azure SDKs in an attempt to modernize its portfolio and make for easier integration with software both within Microsoft and externally.