Ah, I see, you create a factory and then use it instead of creating the Product directly.
In C# we normally use the dependency injection container as the factory (we still use factories on occasion, but for different reasons).
Using the container as the factory, and it being tightly integrated into the web framework, in the controllers, like you can see above, we just add the dependencies we want in the constructor, and the framework passes them in automatically.
public class GroupsController : Controller
private readonly IGroupsService _groupsService;
public GroupsController(IGroupsService groupsService)
_groupsService = groupsService;
class PlayController < Controller
store = Invoice
In Ruby code is like this. Don't need a DI container.
Yupe. Different ways to get to the same end result of decoupling components 🙂
I like the C# approach, probably because I'm used to it, but I can understand that coming from other languages it seems overly complex.
Being able to just declare the dependencies in the constructor and they'll be there when running is nice (even if a bit magic) and gives quick visibility on the dependencies of a given class just by looking at the constructor. It does come with the hidden complexity you talked about, so as always, there are trade offs.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.