what’s a good approach to working with multiple databases?
I’m working on a project that has its own database call it InternalDb, but also it queries two other databases, call them ExternalDb1 and ExternalDb2. Both ExternalDb1 and ExternalDb2 are actually required by a few other projects. I’m wondering what the best approach for dealing with this is?
what’s a good approach to working with multiple databases?
I’m working on a project that has its own database call it InternalDb, but also it queries two other databases, call them ExternalDb1 and ExternalDb2. Both ExternalDb1 and ExternalDb2 are actually required by a few other projects. I’m wondering what the best approach for dealing with this is?
Dependency Injection Confusion
I think I have a decent grasp of what Dependency Inversion principle (DIP) is, my confusion is more around dependency injection.
Dependency Injection Confusion
I think I have a decent grasp of what Dependency Inversion principle (DIP) is, my confusion is more around dependency injection.
Dependency Injection Confusion
I think I have a decent grasp of what Dependency Inversion principle (DIP) is, my confusion is more around dependency injection.
IOC Between Presentation and Infrastructure Layer
Question:
I would like to set forth dependency mapping from a *.config file from a project that has no reference to the project that contains the concrete class.
Database Context and Singleton injection with IoC
All of the below relates to a ASP.NET c# app.
I have a Singleton Settings MemoryCache that reads values from database on first access and caches these, then invalidates them using SQL Service Broker message and re-reads as required.
Database Context and Singleton injection with IoC
All of the below relates to a ASP.NET c# app.
I have a Singleton Settings MemoryCache that reads values from database on first access and caches these, then invalidates them using SQL Service Broker message and re-reads as required.
Database Context and Singleton injection with IoC
All of the below relates to a ASP.NET c# app.
I have a Singleton Settings MemoryCache that reads values from database on first access and caches these, then invalidates them using SQL Service Broker message and re-reads as required.
Is Convention Over Configuration “Knowledge in the World” or “Knowledge In Your Head”?
In Don Norman’s seminal work “The Design of Everyday Things”, the author coined the phrases and explains the difference between “Knowledge in the World” and “Knowledge In Your Head”; an example of this is a multi-switch light panel that can either incorporate “Knowledge in the World” by being a model/map of the room, with the switches in the corresponding location, or “Knowledge In Your Head” (which is how they are almost always designed/implemented) when you have to memorize which switch toggles which light.