tingle 

Event-Based framework for distributed applications.

Shared EventBus transport components for Azure.

Extra validation attributes for application specific scenarios such as dates in the past/future, ratings, prefixes, swift code, and timezones.

Azure Service Bus transport implementation for Tingle.EventBus.

Easier ways to handle optional values especially in libraries.

InMemory transport implementation for Tingle.EventBus (to be used primarily for testing purposes).

Convenience for producing and consuming continuation tokens in AspNetCore

Helpers for making processing of bulk in-memory tasks e.g. in a background thread/task

JSON Patch (https://tools.ietf.org/html/rfc6902) defines a JSON document structure for expressing a sequence of operations to apply to a JavaScript Object Notation (JSON) document; it is suitable for... More information

Validation handlers for phone numbers either via attributes or resolvable services with support for specific MNOs (Mobile Network Providers).

Distributed cache implementation of Microsoft.Extensions.Caching.Distributed.IDistributedCache using MongoDB. For more information, refer to https://www.mongodb.com/.

Azure Queue Storage transport implementation for Tingle.EventBus.

A serializer implementation for Tingle.EventBus using Newtonsoft.Json

Authentication handlers for use with HttpClient and Microsoft.Extensions.Http such as Shared Key, API Key and OAuth

Extensions logging towards Azure LogAnalytics.

Azure Event Hubs transport implementation for Tingle.EventBus.

Shared EventBus transport components for Amazon.

RabbitMQ transport implementation for Tingle.EventBus.

Kafka transport implementation for Tingle.EventBus.

Various serialization functionalities that aren't in the `System.Text.Json` library but may already be in the counterpart `Newtonsoft.Json` library.