Wondering if anyone has used Ninject in a production application? And what pros and cons should one be aware of?
Ninject is a lightweight Dependency Injection framework for . NET applications. It helps you split your application into a collection of loosely-coupled, highly-cohesive pieces, and then glues them back together in a flexible manner.
You can waste days evaluating IOC containers. The top ones are quite similar. There is not much in this, but the best ones are StructureMap and AutoFac.
AutoFac provides better integration for the ASP.NET MVC framework and is developed using Google code. AutoFac manages the dependencies of classes so that the application may be easy to change when it is scaled up in size and complexity.
Ninject is and will always be free for both personal and commercial projects. It's also open source, so you can fork the code and make any changes you like.
Depends what sort of production applications. Generally speaking, I've deployed it to a couple of production apps without any problems. Having said that, the scale that those apps required was only a few hundred concurrent connections and it handled it fine. If you're talking about millions of concurrent connections you should probably do your due diligence and do some prototyping first.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With