blocks|key|3715155|text|没有什么大问题。Spring特别有益于：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3715156|为Hibernate|3715157|Declarative+Transaction+Demarcation|unordered-list-item|3715158|
|3715159|The+Acegi+(现在的+Security)项目提供更好的code|3715160|Declarative+"Open+Session+In+View“功能支持的Spring+|3715161|使得集成自定义安全模型变得很容易。|3715162|数据访问支持消除了对任何访问的大量模板的需要--也许对Hibernate的使用没有那么大的促进作用，但是我们有两者的混合。它还允许您将JDBC和Hibernate无缝地结合在一起使用。|3715163|3715164|3715165|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|X|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|Y|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|Z|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|10|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|11|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|T|$]]

No major issues. Spring was particularly of benefit for:

<ul>
<li>Making all the configuration plumbing consistent and straightforward</li>
<li>Dependency Injection to support better factoring of code</li>
<li>Declarative "Open Session In View" functionality for Hibernate</li>
<li>Declarative Transaction Demarcation</li>
<li>The Acegi (now Spring Security) project made it easy to integrate a custom security model</li>
<li>The Spring data access support removes the need for a lot of boilerplate from any JDBC access - maybe not such a boost for Hibernate usage, but we had a mix of both. It also allows you to use JDBC &amp; Hibernate together fairly seamlessly</li>
</ul>

blocks|key|3715235|text|除了到目前为止已经说过的，我将专注于Spring+(例如@Controller)和Hibernate+(例如@Entity)的更新风格的注释。它将进一步减少你的代码量，减少你需要维护的代码。在不利的方面，有一个相当重要的学习曲线，但最终我一次又一次地学到的教训是，Spring+%2B+Hibernate的好处远远超过(学习曲线)成本。你只需要编写更少的代码，让你专注于业务。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3715236|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In addition to what has been said so far, I would focus on newer style annotations for both Spring (e.g. @Controller) and Hibernate (e.g. @Entity). It will further reduce your codebase leaving you with less code to maintain. On the downside, there is a pretty significant learning curve, but ultimately the lesson I learn time and again is that the benefits of Spring + Hibernate far outweigh the (learning curve) costs. You simply have to write a lot less code letting you focus on the business.

blocks|key|4560646|text|%2B1+Spring%2Bhibernate......|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4560647|10万用户不是中等规模的……这是很大的规模。|4560648|使用spring，您可以强制程序员对接口进行编码，这提高了可测试性。这是我没有听到人们谈论太多的好处。|4560649|查看memcached+to+cached+data+memcached.....|offset|length|4560650|entityMap|0|LINK|mutability|MUTABLE|url|http://www.danga.com/memcached/^0|0|0|0|R|9|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@$H|V|I|W|1|X]]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

+1 Spring+hibernate......

100k users is not mid-size....that is huge.

With spring, you can force coder to code to interfaces and this increase testability. This is the benefit i don't hear people talk a lot about.

take a look memcached to cached data <a href="http://www.danga.com/memcached/" rel="nofollow noreferrer">memcached</a>.....

blocks|key|3715520|text|从技术上讲，我已经使用spring和hibernate部署了从数千到几十万的商业应用程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3715521|在一个案例中，从管理的角度来看，我有一个团队，他们是优秀的技术专家，所以他们设法用spring和hibernate重写了一个应用程序，但是……他们疯狂地使用接口(模型中的每个新对象都需要16个接口)，滥用AOP，因此事务和日志记录几乎不可能跟踪，堆栈跟踪毫无意义，使用工具映射hibernate文件，而不完全了解正在做什么(在某些情况下，为了一个简单的实体而连接4个表，以及各种问题，这些问题使得最终的应用程序更难增强、调试、修复，甚至设置开发人员的环境……)|3715522|我的2c|3715523|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

techincally speaking I have, I've deployed commercial applications with numbers from the thousands to a few hundreds of thousands using spring, hibernate and both.

From the management perspective in one case, I had a team that were good technologists, so they managed to rewrite an app with spring and hibernate but... they went crazy with the interfaces (each new object to the model needed 16 interfaces), abused the AOP so transactions and logging were almost impossible to follow and stack traces were meaningless, used tools to map the hibernate files without fully understanding what was being done (in some cases joining 4 tables for what could've been a simple entity, and a variety of issues that made the resulting application much harder to enhance, debug, fix, even setup the developer's environment....)

my 2c

blocks|key|495807|text|正如Julien+Chastang所说，如果这是您的第一个项目，那么您需要在评估中考虑学习曲线。我们在第一次尝试时没有做到这一点，最终不得不调整我们的许多计划，因为Hibernate的几个方面是“困难的”(例如。花了一些时间)才弄明白。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|495808|根据我们遇到的一个问题，我可以给出一个具体的建议:如果你需要编写复杂的SQL，并且你不想花时间弄清楚如何在HQL或Hibernate中的其他产品中使用这样的查询，那么首先让它在普通SQL中工作，然后再回到Hibernate中。|495809|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

As Julien Chastang said, you need to factor in the learning curve in your estimations if this is your first project. We failed to do that on our first try and ended up having to adjust a lot of our planning because several aspects of Hibernate were "hard" (eg. took some time) to figure out.

One specific piece of advice I can give based on an issue we came across is: if you need to write complex SQL, and you don't want to spend the time figuring out how to get such queries working within HQL or other offerings within Hibernate, get it working first in vanilla SQL and then go back later and patch it back into Hibernate.

blocks|key|3715082|text|显然，无论是在java框架的世界中，还是使用Rails或Django之类的东西来构建这样的应用程序，都有上百万种方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3715083|对我来说，一个很大的卖点是，spring和hibernate都已经成为java世界中事实上的标准，所以它们绝对可以被归类为“你应该知道的事情”(我在每次面试中都会被问到)。比起冬眠，Spring更是如此。|3715084|在我理解spring的意义之前，我花了几个启用了spring的应用程序来获取spring的价值。它强制执行独立的代码模块和某种风格的组件设计，以便于测试。我建议你直接使用它，并从使用中感受到它的价值。|3715085|我对Hibernate的感觉很复杂，尽管使用某种db层很重要，所以你也可以。|3715086|另请参阅this+question.|offset|length|3715087|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/100243/java-frameworks-war-spring-and-hibernate/142029#142029^0|0|0|0|0|4|E|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@$J|Y|K|Z|1|10]]|A|$]]|$1|L|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

Obviously there are a million ways to build an application like this, both in the java frameworks world and with things like Rails or Django. 

A big selling point for me is that both spring and hibernate have become defacto standards in the java world, so they definitely qualify as "things you ought to know" ( I get asked on every job interview). Spring more so than Hibernate.

Getting the value of spring took a few spring-enabled apps before it made sense for me. It enforces independant code modules and a certain style of component design that facilitates testing. I'd suggest you just go with it and get the sense of the value of it from use.

I have mixed feelings about Hibernate, though it's important to use some kind of db layer, so you may as well.

Also see <a href="https://stackoverflow.com/questions/100243/java-frameworks-war-spring-and-hibernate/142029#142029">this question.</a>

blocks|key|4560761|text|在使用Hibernate的某些情况下，创建特定的对象到关系的映射或编写特定的HQL查询非常困难。然而，您将遇到10个中的1个，并且数据库的规范化程度越高，您的情况就越好。这是值得的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4560762|任何新的Java+web项目都应该使用Spring+MVC+(带注释的2.5%2B)和Hibernate。|4560763|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

There are some situations with Hibernate where creating a particular object to relational mapping, or writing a particular HQL query, is very difficult. However, you're going to run into 1 thing like that out of 10, and the more normalized your database the better off you will be. It's worth it. 

Any new Java web project should use Spring MVC (2.5+ with Annotations) and Hibernate.

blocks|key|4560815|text|对hibernate和spring有大量的理解开销。只有当你有足够的时间或者有经验的java/spring/hibernate开发人员可以访问时，我才会建议你这样做。对于spring项目，一旦你开始运行它，你基本上可以忽略它的spring部分，而专注于页面和逻辑设计。Hibernate并没有那么难。HQL是一个更难的要求。我的大部分时间都花在bean和JSF级别上。将我的项目的这一层与一些在JSP中胡闹的伙伴进行比较，我很高兴能够轻松地使用JSF。我很容易从最初的MySQL实现切换到Oracle，所以这证明Hibernate很好地处理抽象。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4560816|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

There is a large understanding overhead to hibernate and spring. I'd only suggest it if you have plenty of time or an experienced java/spring/hibernate developer to call on. With a spring project once you get it going you can basically ignore the spring parts of it and concentrate on page and logic design. Hibernate is not that difficult. HQL is a harder ask. Most of my time is spent at the bean and JSF level. Comparing that layer of my project to some mates who are messing about in JSP, I'm glad to be in the ease of JSF. I easily swapped to Oracle from the initial implementation in MySQL, so that proves that Hibernate handles abstraction nicely.

blocks|key|4560910|text|除了到目前为止所说的，我强烈建议这本书：Spring+Recipes+-+Problem+Solution+Approach+(Amazon)，结合非常好的在线文档，你应该准备好征服世界;-)|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4560911|entityMap|0|LINK|mutability|MUTABLE|url|https://rads.stackoverflow.com/amzn/click/com/1590599799^0|K|1F|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

in addition to what has been said so far, i strongly suggest the book: <a href="https://rads.stackoverflow.com/amzn/click/com/1590599799" rel="nofollow noreferrer" rel="nofollow noreferrer">Spring Recipes - Problem Solution Approach (Amazon)</a>, in combination with the very good online documentation you should be ready to conquer the world ;-)

I am working on medium sized web application 4-5 tabs, user login for about 100k users. We are completing redesigning the application from scratch and using spring and hibernate, connected to MySQL.

Did you experience major issues and what where did Spring benefit your application.

Have you found success with a Spring and Hibernate Web Application

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我在中型网络应用程序4-5标签，用户登录约100k用户工作。我们正在从头开始重新设计应用程序，并使用spring和hibernate，连接到MySQL。您是否遇到过重大问题? Spring给您的应用程序带来了哪些好处？

问您是否发现Spring和Hibernate Web应用程序取得了成功
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问您是否发现Spring和Hibernate Web应用程序取得了成功EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问您是否发现Spring和Hibernate Web应用程序取得了成功
EN