Skip to content

Release v21.0.0

Choose a tag to compare

View all tags
@dolittle-build dolittle-build released this 20 Jan 15:28
v21.0.0
68d39ef
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Summary

Major improvements to the Dolittle Client, in how it connects to the Runtime, configuration, setup an integration with ExpressJS. Combined these changes aim to make the SDK easier to setup and configure, and to make it easier to detect when incompatible versions are used.

Added

  • Support for Dependency Injection using Inversify internally, with support for TypeDi and TSyinge, also supporting tenant-specific bindings.
  • The DolittleClient and tenant specific resources (IEventStore, IAggregates, IProjections, ...) are bound in the service provider used and exposed by the client. They can be used in for example Event Handlers, or with the ExpressJS integration in request handlers.
  • Express integration through .use(dolittle()) on express , starts the DolittleClient and sets it up with default configurations if not explicitly provided, starts a middleware that makes the DolittleClient resources available on the request based on the Tenant-ID header (provided by the platform). See the ExpressJS sample.
  • By default auto discover all aggregate roots, event types, event handlers, projections and embeddings
  • When starting up a DolittleClien, it now performs an initial handshake with the configured Runtime to determine that the version of the SDK and the Runtime are compatible, and retrieves the MicroserviceId to configure its executions context (provided by the platform).

Changed

  • Building a DolittleClient is two steps, namely .setup() and .connect(), to make integrations easier.
  • The configured Tenants are retrieved during the first connection to the Runtime, so the .tenants on the DolittleClient Is no longer an asynchronous call.
  • The builder APIs exposed in the .setup(...) call have been changed so they are all called .register() or .create() and removed the .build() methods
  • The aggregateOf() methods on the client have been changed to an Aggregates property that behaves like the other tenant specific resources.

Fixed

  • The SDK de-duplicates registered types and processors (Event Handlers, ...) so that you can use both automatic discovery and manual registration.

Removed

  • .build() methods no longer exposed on the builder API
Assets 2
Loading