Explore >> Select a destination
|
You are here 
|
conradakunga.com | ||
| | | | |
tomasvotruba.com
|
|
| | | | | While working with legacy projects, I often encountered this anti-pattern of misusing repositories. Instead of easy-to-inject service, projects are locked into a service locator. This makes code hard to upgrade and locks your project heavily to the Doctrine ODM packages. And there are plenty of them. Each extra package bites off its share of upgrade costs. Today, we look at how to refactor the ODM service locator to independent services and separate your project from ODM. We also get a few advantages in strict type coverage. | |
| | | | |
csharp.christiannagel.com
|
|
| | | | | ASP.NET Core included the WebHost class that was used in the Main method to startup everything up - including the dependency injection container. With Non-ASP.NET Core applications I used the same DI container (Microsoft.Extensions.DependencyInjection), but I had to create the ServiceCollection on my own. This changes with .NET Core 3.0 and the new Host class... | |
| | | | |
nodogmablog.bryanhogan.net
|
|
| | | | | Full source code available here. Did you know that .NET Core 2 can pass in an instance of any type you want to the Startup.cs constructor? Well you can! Here's how. | |
| | | | |
sookocheff.com
|
|
| | | Microservices have become part of the software engineering cultural zeitgeist to the extent that alternative approaches to architecture and development are treated as somehow inferior. Given the challenges that running microservices present, I usually recommend beginning development of new projects and systems as a single deployable unit - the monolith. Sam Newman, in the book "Building Microservices", agrees with this approach. He recommends leveraging microservices only if you can become convinced of the benefits for your system, not as a default for every project. | ||
