azure-sdk-for-net
spec
Our great sponsors
azure-sdk-for-net | spec | |
---|---|---|
22 | 31 | |
4,964 | 4,756 | |
0.7% | 2.9% | |
10.0 | 7.5 | |
5 days ago | 14 days ago | |
C# | Python | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
azure-sdk-for-net
-
Fellow Rust enthusiasts: What "sucks" about Rust?
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:
- Example of a well designed modern .Net SDK
-
How to use Azurite for testing Azure Storage in dotnet?
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.
-
Obtain Azure access token from a local Docker container
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.
- Programmatically add to Azure IP Filtering List
-
Case Study: Azure Service Bus and Event-Driven Architectures
In a distributed system, many things can go wrong. The network can fail or have additional latency, systems may be temporarily down, etc. We use the Azure.ServiceBus.Messaging NuGet package so we are able to check if the exception is a transient fault or not (more information on these docs), then use Polly to setup retry logic and fallbacks. There are other options to implement retry policies, for example we took in consideration the Retry guidance for Azure Services documentation from Microsoft. Since we use the latest Azure SDK, the appropriate class would be ServiceBusRetryPolicy.
-
KeyVault Secrets Rotation Management in Bulk
Then, create the SecretClient that accesses the Key Vault instance. While instantiating the client, you should provide the DefaultAzureCredentialOptions instance as well. If the account logged into Azure is able to access multiple tenants, you should explicitly provide the tenant ID; otherwise, it throws the authentication error (line #4-6).
-
Subscription level disk utilization/rightsize analysis
ugh ... Azure makes some of these things very difficult to track down. For example, I'm not sure this is your specific case, but it sounds related (or at least familiar) - https://github.com/Azure/azure-sdk-for-net/issues/3318#issuecomment-306380182
-
Processing CloudEvents for Azure EventGrid via Azure Functions
I used .NET SDK in this post. But there are other SDKs in different languages of your choice:
spec
-
Data Streaming Architecture
The structure of this example message is using CloudEvents specification:
- FLaNK Stack Weekly 27 March 2023
-
Show HN: Automatisch – open-source workflow automation, an alternative to Zapier
CloudEvents is trying to standardize on the messaging
- FLiP Stack Weekly for 21 Jan 2023
-
A message queue focus on serverless program
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
-
An alternative look at workflows in cloud era
Lastly, workflow as a function flow in Automatiko is also based on Funqy, but this time it leverages Knative project to build function chaining based on events (Cloud Events). Knative is a kubernetes based platform to deploy and manage modern serverless workloads. In particular, Knative eventing comes with universal subscription, delivery and management of events that allows to build modern applications by attaching business logic on top of the data stream - the events.
-
Google Cloud Functions 2nd gen
One of the most exciting 2nd gen functionality is the ability to create functions of Cloud Events type. These are event functions that, instead of receiving an event in a proprietary Google Cloud format, will receive one in a standard format as described in the Cloud Events specification.
-
GraphQL for Event Driven Architecture
Curious why you decided to go for GraphQL instead of something like Cloud Events spec (https://cloudevents.io)
-
What's your experience with event driven?
There is also https://cloudevents.io but I have never used it.
-
Getting Started with CloudEvents and AsyncAPI
There are a few extensions worth mentioning, one of them is for distributed tracing. However, it seems there is some discussion around removing this extension from the spec (check this PR on GitHub). There are open issues on some SDKs to support it, and others have already made changes to remove it. The future isn't clear, but I'd argue it's interesting to follow this closely for any updates, since tracing events is very important in an event-driven architecture.
What are some alternatives?
keptn - Cloud-native application life-cycle orchestration. Keptn automates your SLO-driven multi-stage delivery and operations & remediation of your applications.
asyncapi-to-postman - Creates a Postman collection from an AsyncAPI file.
steampipe - Zero-ETL, infinite possibilities. Live query APIs, code & more with SQL. No DB required.
cupid - A library that focuses on finding and analyzing the relationships between AsyncAPI documents. It outputs a map of the system architecture. Except for a default map, it is possible to get output as mermaid.js flow diagram, PlantUML class diagram and more to come.
youtube-websub-subscription-handler - This is a WebSub subscription handler for YouTube video feed update | YouTube 비디오 피드 업데이트를 WebSub 기능을 이용해 받아 처리합니다
generator - Use your AsyncAPI definition to generate literally anything. Markdown documentation, Node.js code, HTML documentation, anything!
PowerPlatformConnectors - This is a repository for Microsoft Power Automate, Power Apps, and Azure Logic Apps connectors
k8s-event-grid-bridge - A simple event bridge for Kubernetes native events to Azure Event Grid.
specification - Serverless Workflow Specification
PubSubHubbub - The PubSubHubbub protocol specification.
litmus - Litmus helps SREs and developers practice chaos engineering in a Cloud-native way. Chaos experiments are published at the ChaosHub (https://hub.litmuschaos.io). Community notes is at https://hackmd.io/a4Zu_sH4TZGeih-xCimi3Q
blackbox_exporter - Blackbox prober exporter