title: Ninject modules or organising wiring up dependencies
body: <p>I've started playing with Ninject and from a screencast it states the following is how you set up a binding:</p>
  
  <pre><code>class MyModule : StandardModule {
  
      public override void Load() {
          Bind&lt;IInterface&gt;().To&lt;ConcreteType&gt;();
          // More bindings here...
      }
  }
  </code></pre>
  
  <p>This is all very good.</p>
  
  <p>However suppose you have one hundred objects used in an application. That would mean this would have one hundred bindings. Is this correct?</p>
  
  <p>Secondly, I presume that given such an application it may be split into subsystems such as GUI, Database, Services and so on.</p>
  
  <p>Would you then create a custom module for each subsystem which in turn would be:</p>
  
  <ul>
  <li>GUIModule </li>
  <li>DatabaseModule</li>
  <li>ServiceModule </li>
  <li>...</li>
  </ul>
  
  <p>For each module you'd have the correct bindings that they required. Am I on the right page here?</p>
  
  <p>Finally would this binding all occur in <code>Main</code> or the entry point for your application?</p>