title: Why Does Ignite Use Spring framework?
body: <p>I had used Spring framework in my apps and while it is nice conceptually, it is not suitable for real-time apps due to its run-time overhead. For instance, <a href="http://apache-ignite-users.70518.x6.nabble.com/Failed-to-map-keys-for-cache-all-partition-nodes-left-the-grid-td23510.html" rel="nofollow noreferrer">http://apache-ignite-users.70518.x6.nabble.com/Failed-to-map-keys-for-cache-all-partition-nodes-left-the-grid-td23510.html</a> shows the actual run-time Spring stack. </p>
  
  <p>The Spring features that Ignite uses for loading application-defined beans are just many layers wrapped around simple Java reflection features. So Why Ignite uses Spring instead of straight Java'reflection ?  </p>
  
  <p>To make Ignite more performant, is there plan with Ignite to switch from Spring framework to Java reflection features ?</p>
  
  <p>Similarly, if Ignite uses Spring Boot to handle port requests, why does it not use a light-weight framework such as www.sparkjava.com ?</p>