Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sam: Copy Projection read models to MongoDB for querying #614

Merged
merged 67 commits into from
Feb 9, 2022
Merged

Conversation

jakhog
Copy link
Contributor

@jakhog jakhog commented Jan 25, 2022

Summary

Introduces secondary storage mechanisms for Projection read models, this enables using existing databases as query engines for read models. The Projections that should be copied, are stored in Collections in the MongoDB resource for the Microservice, so that they can be accessed through the MongoDB resource in the SDKs. These collections will be created and dropped as per the copy specification in the Projection registration request. These collections should only be read from the client, and not modified - as this can cause strange behaviour.

Added

Changed

  • The Dolittle CLI now includes container names in the Runtime selection list when multiple Runtimes are detected.

@jakhog jakhog added the minor label Jan 25, 2022
jakhog and others added 28 commits January 25, 2022 18:36
Co-authored-by: Sindre Alstad Wilting <woksin@users.noreply.github.com>
Handle the Projection copies registration arguments
jakhog and others added 25 commits February 3, 2022 17:59
Still more specs needed for this one.
In case it has seemingly colliding renamings that is actually fine.
…cture

Renaming and new contracts structure
…o let the ValueConverter decide the format properly.
Set GuidRepresentation for the MongoDB copy storage to Unspecified
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants