06 ‐ Feedback
| Subject | Description |
|---|---|
| Memory context | Built with StackExchange Redis library |
| Lazy concept | Our entity will be defined inside controller constructors |
| Global repository | Only one dynamic repository was built |
| Injection | Context and repository are only items |
| Configuring | Set a database index for different purposes |
| Subject | Description |
|---|---|
| Document context | Built with Mongo Driver library |
| Configuration | Defined on app-settings.json |
| Specialized repository | Small persistance part for opt (in/out) |
| Injection | Context and repository are only items |
| Domain | There's only one entity |
Here's an example of how to implement a infrastructure provider in our project, below there's a document db.
Start by creating all contexts and interfaces with specialized objects.
Then, define what your repository will be able to perform on a centralized interface (injected in a future).
After setup, you can inject your interface (considering you've already implemented it properly too).