The Azure Web PubSub Service can be used for real-time messaging applications using web sockets and the publish-subscribe pattern. We use subprotocol json.webpubsub.azure.v1 to exchange messages in JSON format. The actual xml message is a passed as a string via the data node.
PaaS vNext means you can deploy Azure Web Apps, Functions, Logic Apps, API Management and EventGrid to an Arc-enabled Kubernetes cluster, so not as a PaaS offering in the public cloud. Arc-enabled means that you can run the cluster anywhere: in an Azure VM, in the Amazon cloud, on the Google cloud platform or on premises. All in your own private compute space.
There’s a new interesting feature to secure your Azure Function via a Bearer Authorization token (preview). Use the OpenAPI Extension for Functions. It’s interesting if you don’t wanna use API Management.
Ideally Integration and BI work together on data ingestion, especially when the primary applications are outsourced to independent software vendors. But most often there’s no such cooperation. How come? Looking at the Lambda and the Kappa Architecture can be an interesting angle to reflect on the issue.
Architectural work often isn’t assigned to sprints. It’s better to put epics, features and user stories on the backlog and leave it there. No rocket science, but it saves you a lot of work.
Example of how to validate a Json Web Token (JWT) and retrieve a value from that JWT via an API Management policy.
To parameterize a logic app with a secret value, you can use a parameter of type securestring in your logic app. In the parameter file, when specifying the value for the securestring parameter, you can refer to your keyvault instance and secretname.
The CIA triad is a widely used information security model. It’s an acronym for Confidentiality, Integrity, Availability. The Dutch equivalent is BIV, which stands for: Beschikbaarheid, Integriteit, Vertrouwelijkheid.
To deploy an ARM template for an API Management service without using a storage account, you can use so called nested templates in your orchestrator file.
To get authorization working with an OAuth2 token v2.0 using the ValidateJWT policy in API Management, call the token endpoint with scope api://[ClientId Service]/.default.