Spring框架绝对适合web开发，尤其适合restful api服务。

这是因为它的依赖注入和与其他模块的集成，如spring security、spring aop、mvc框架、微服务

在任何应用程序中，安全性都很可能是一个需求。 如果您的目标是构建一个需要长期维护的产品，那么您将需要利用Aop的概念。 如果你的应用程序有太多的流量，从而增加了负载，你需要使用微服务的概念。

Spring在一个平台中提供了所有这些特性。支持多个模块。 最重要的是，spring是开源的和可扩展的框架，在生命周期中到处都有钩子来集成自定义代码。

Spring Data是一个提供与您的项目集成的项目。

所以弹簧几乎可以满足所有的需求。

其优点是依赖注入(DI)。这意味着将对象创建任务外包出去。让我用一个例子来解释。

public interface Lunch
{
   public void eat();
}

public class Buffet implements Lunch
{
   public void eat()
   {
      // Eat as much as you can 
   }
}

public class Plated implements Lunch
{
   public void eat()
   {
      // Eat a limited portion
   }
}

现在在我的代码中，我有一个类LunchDecide，如下所示:

public class LunchDecide {
    private Lunch todaysLunch;
    public LunchDecide(){
        this.todaysLunch = new Buffet(); // choose Buffet -> eat as much as you want
        //this.todaysLunch = new Plated(); // choose Plated -> eat a limited portion 
    }
}

在上面的类中，根据心情选择Buffet()或Plated()。但是这个系统是紧密耦合的。每次需要不同类型的对象时，我们都需要更改代码。在本例中，注释掉一行!假设有50个不同的人使用50个不同的类。那会是一团乱麻。在这种情况下，我们需要解耦系统。让我们重写LunchDecide类。

public class LunchDecide {
    private Lunch todaysLunch;
    public LunchDecide(Lunch todaysLunch){
        this.todaysLunch = todaysLunch
        }
    }

Notice that instead of creating an object using new keyword we passed the reference to an object of Lunch Type as a parameter to our constructor. Here, object creation is outsourced. This code can be wired either using Xml config file (legacy) or Java Annotations (modern). Either way, the decision on which Type of object would be created would be done there during runtime. An object would be injected by Xml into our code - Our Code is dependent on Xml for that job. Hence, Dependency Injection (DI). DI not only helps in making our system loosely coupled, it simplifies writing of Unit tests since it allows dependencies to be mocked. Last but not the least, DI streamlines Aspect Oriented Programming (AOP) which leads to further decoupling and increase of modularity. Also note that above DI is Constructor Injection. DI can be done by Setter Injection as well - same plain old setter method from encapsulation.

Spring非常适合将类实例粘合在一起。你知道你的Hibernate类总是需要一个数据源，Spring将它们连接在一起(也有一个数据源的实现)。

数据访问对象总是需要Hibernate访问，Spring将Hibernate类连接到dao中。

此外，Spring基本上为您提供了一系列库的可靠配置，并指导您应该使用哪些库。

Spring真的是一个很棒的工具。(我说的不是Spring MVC，只是基本框架)。

你可能想在一个web应用程序中使用Spring -

Spring MVC, which with 2.5+ allows you to use POJOs as Controller classes, meaning you don't have to extend from any particular framework (as in Struts or Spring pre-2.5). Controller classes are also dead simple to test thanks in part to dependency injection Spring integration with Hibernate, which does a good job of simplifying work with that ORM solution (for most cases) Using Spring for a web app enables you to use your Domain Objects at all levels of the application - the same classes that are mapped using Hibernate are the classes you use as "form beans." By nature, this will lead to a more robust domain model, in part because it's going to cut down on the number of classes. Spring form tags make it easier to create forms without much hassle.

此外，Spring是巨大的——所以在web应用程序中使用很多其他的东西你可能会感兴趣，比如Spring AOP或Spring Security。但上面列出的四件事描述了Spring在web应用程序中使用的常见组件。

Spring最初是一个相当简单的依赖注入系统。现在它很大，里面什么都有(除了众所周知的厨房水槽)。

但不用担心，它是模块化的，所以你可以只使用你想要的部件。

去看看一切从哪里开始尝试:

http://www.amazon.com/Expert-One-Design-Development-Programmer/dp/0764543857/ref=sr_1_1?ie=UTF8&s=books&qid=1246374863&sr=1-1

它可能很旧，但却是一本好书。

关于另一本关于春天的好书，请看:

http://www.amazon.com/Professional-Java-Development-Spring-Framework/dp/0764574833/ref=sr_1_2?ie=UTF8&s=books&qid=1246374863&sr=1-2

它还引用了较老版本的Spring，但绝对值得一看。

简而言之，我认为Spring是应用程序中的“粘合剂”。它用于集成不同的框架和您自己的代码。