spec VS azure-sdk-for-net

The structure of this example message is using CloudEvents specification:

Microsoft has expanded the Event Grid capabilities to enhance system interoperability by introducing support for MQTT v3.1.1 and v5.0 protocols. This allows customers to publish and subscribe to messages for Internet of Things (IoT) solutions. This new support, currently available in public preview, complements the existing support for CloudEvents 1.0.

You are looking for https://cloudevents.io/ . That is what you should use if you plan to do homegrown. I would however recommend you to use use segment + amplitude, juno, mixpanel . If you are early these are mostly free up to a point.

When modeling an event in a streaming application, what "meta" fields to you use? Like timestampts, versions, some context etc... I think there are some efforts to introduce a standard format like Cloud Events but wondering if you guys have any different suggestions?

CloudEvents is trying to standardize on the messaging

https://cloudevents.io/

Hello guys, actually, vanus can directly deliver messages to OpenFaaS without this kind of connector. Because vanus can deliver messages that follow the CloudEvents standard, OpenFaaS can also receive such messages. More details https://docs.linkall.com/how-to/use-gcloud-functions

Microsoft.Extensions.Azure is an extension library that allows for uniform integration of the Azure SDK into your applications, while giving you the necessary flexibility to customize the behavior of the created Azure SDK clients. The use of named clients is particularly convenient for supporting multiple instances of the same Azure resource type. You also get free logging as the Azure SDK events are automatically forwarded to an ILogger instance.

Semantic Search sample

You should be able to do something like these examples, as long as they have the same primary key.

So how do you download part of a blob from Azure? Well, in https://github.com/Azure/azure-sdk-for-net/releases/tag/Azure.Storage.Blobs_12.12.0 there's a function that looks like this:

Now granted these tokens do have some limitations as pointed out in the docs. But based on this answer from an Azure dev on Github: https://github.com/Azure/azure-sdk-for-net/issues/18108

The testing helpers have more to it than disabling SSL but are not present on NuGet. So naturally, I raised an issue to the SDK team if they have any plans in that direction. Unfortunately, at this point, they have no interest in releasing their internal test tooling. The techniques I mentioned thus far can be used standalone. I, however, felt this was an excellent opportunity to create my first NuGet Package. The package cannot assume how anybody runs Azurite, so I introduced two classes. You can use AzuriteAccountBuilder to configure how things are run, like the account or the ports being used. The AzuriteAccount class provides access to stuff like the connection string. For convenience the package also creates helper methods to create BlobServiceClient, TableServiceClient or QueueServiceClient form an AzuriteAccount.

This seems either a bug in the Azure SDK or in the Service Bus itself, I'm not the only one that ran into this issue and here you can find additional information.

Q: I can obtain tokens locally using Azure CLI and Azure.Identity library when I run on the host machine, but not when inside Docker container because it doesn't have Azure CLI installed! What do I do? A: This has already been asked about by many people here with various interesting solutions here and here.