gigya 

Interface abstractions used by various Microdot components, seperated from their implementations to allow easy unit testing with mocks (see Gigya.Microdot.Fakes). Part of the Microdot Framework.

Various components and utilities shared between different parts of the Microdot framework.

A configuration system based on a hierarchy of XML files, the values of which are accessed using strongly-typed configuration objects. Supports modification of the files on live service, environment variable substitution, encryption and collections. Part of the Microdot framework.

Ninject modules, providers and binding resolvers for various Microdot components, part of the Microdot framework.

Infrastructure used for hosting Microdot services, part of the Microdot framework.

A Collection of fakes for various Microdot components, used for testing. Part of the Microdot framework. See also Gigya.Microdot.Testing.

ServiceProxy is used to call remote Microdot services. It is a runtime-generated transparent proxy which implements the remote service's public interface, translating all calls performed on it to HTTP calls. Part of the Microdot framework.

Using this component you can find other Microdot services (and any other remote system), perform client-side load balancing between multiple servers, detect and skip unresponsive servers and resume using them when they return to full operation. Discovery is typically perfomed with Consul by... More information

Infrastructure used for hosting Orleans Microdot services, part of the Microdot framework.

A container used to host an Orleans Microdot service which uses Ninject for dependency injection. Incoming HTTP calls (via Gigya.Microdot.ServiceProxy) are handled and processed inside Orleans and are then dispatched to specific Grains. Part of the Microdot framework.

A container used to host non-Orleans Microdot service which uses Ninject for dependency injection. Incoming HTTP calls (via Gigya.Microdot.ServiceProxy) are dispatched to a specified class instance. Part of the Microdot framework.

Tools to help write tests for Microdot services.

An implementation of Microdot's logging and tracing using NLog.

Referenced by microservice public-facing interfaces. Provides common facilities that are needed to define a service's contract. Part of the Microdot framework.

Tools to help write tests for Microdot services.

Provides high and low level classes for communicating with an Apache Kafka cluster. A fork of kafka-net by Jroland, with improvements and adjustments (see project site).

An Orleans PersistentStreamProvider based on Kafka