Referenced by microservice public-facing interfaces. Provides common
facilities that are needed to define a service's contract. Part 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.
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.
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.
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...
More information
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.
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.
