DI Container usage
The eridu-tech/di component provides an Inversion of Control (IoC) container for managing service registrations, dependency resolution, and object lifetimes.
The eridu-tech/di component provides an Inversion of Control (IoC) container for managing service registrations, dependency resolution, and object lifetimes.
The lockFactoryResolverDiFactory function creates an ILockFactoryResolver whose underlying resolver is resolved from a DI container.
The semaphoreFactoryResolverDiFactory function creates an ISemaphoreFactoryResolver whose underlying resolver is resolved from a DI container.
The sharedLockFactoryResolverDiFactory function creates an ISharedLockFactoryResolver whose underlying resolver is resolved from a DI container.
The ProxyExecutionContext class provides an IExecutionContext whose underlying execution context is resolved from a DI container.
The ProxyTransactionContextResolver class provides an ITransactionContextResolver whose underlying resolver is resolved from a DI container.
The ProxyEventBusResolver class provides an IEventBusResolver whose underlying resolver is resolved from a DI container.
The circuitBreakerFactoryResolverDiFactory function creates an ICircuitBreakerFactoryResolver whose underlying resolver is resolved from a DI container.
The rateLimiterFactoryResolverDiFactory function creates an IRateLimiterFactoryResolver whose underlying resolver is resolved from a DI container.
The cacheResolverDiFactory function creates an ICacheResolver whose underlying resolver is resolved from a DI container.
The fileStorageResolverDiFactory function creates an IFileStorageResolver whose underlying resolver is resolved from a DI container.
The bindHttpFactory function turns a controller method into an HttpHandlerFn. This lets you keep HTTP handlers on injectable controller classes and resolve them from a DI container for every request, instead of wiring handler functions to service instances manually.