Java 应用程序架构指南
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/647922/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
Java Application Architecture Guide
提问by yoitsfrancis
Is there a Java Application Architecture Guide that is a counterpart of this: http://www.codeplex.com/AppArchGuide?
是否有与此对应的 Java 应用程序架构指南：http: //www.codeplex.com/AppArchGuide？
采纳答案by Swapnonil Mukherjee
The following should be helpful to you
以下应该对你有帮助
- Core J2EE Patterns
- Effective Enterprise Java
- Patterns of Enterprise Application Architecture
- Head First Design Patterns
- J2EE Blueprints
- Sun Certified Enterprise Architect, Study Guide
Although, having had a quick glance at the document from codeplex, I can tell you that probably 70-80% of what is in there, applies to Java as well.
尽管快速浏览了 codeplex 中的文档，但我可以告诉您，其中可能有 70-80% 的内容也适用于 Java。
回答by duffymo
I apologize for not reading the very nice link you provided.
我很抱歉没有阅读您提供的非常好的链接。
I will say that architecture ought to be a language-independent sort of thing. Once you understand the principles it ought to be a matter of mapping the features and implementation details of one platform onto the other.
我会说架构应该是一种与语言无关的东西。一旦您理解了原则，就应该将一个平台的功能和实现细节映射到另一个平台上。
I hesitate to post links to any Java EE standards, because the changes made in going to EJB 3.0 make a lot of the "best practices" of earlier versions obsolete.
我不愿发布任何 Java EE 标准的链接，因为在向 EJB 3.0 过渡时所做的更改使得早期版本的许多“最佳实践”已经过时。
Object-relational mapping is now embodied in JPA; Spring has introduced ideas like dependecy injection and aspect-oriented programming.
对象关系映射现在体现在 JPA 中；Spring 引入了诸如依赖注入和面向方面编程之类的思想。
Right now I'd say that studying Springwould give you the best insight into Java best practices for enterprise architecture.
现在我想说的是，学习Spring将使您对企业架构的 Java 最佳实践有最好的了解。
回答by Jens Schauder
I am still downloading the document referenced, but from the description of the page I would think
我仍在下载引用的文档，但从页面的描述中我认为
a) A lot of it should be language independent, so it should apply to java as well.
b) Patterns of Enterprise Application Architecture might fit. (this as well is Platform/language independent.) You can read about the book here http://martinfowler.com/books.html
a) 很多应该是独立于语言的，所以它也应该适用于 java。
b) 企业应用架构模式可能适合。（这也与平台/语言无关。）您可以在此处阅读有关这本书的信息http://martinfowler.com/books.html
Edit:
I just skimmed over the document. Looks really interseting. I guess I need to spend some more time with it.
编辑：
我只是浏览了文档。看起来真的很有趣。我想我需要花更多的时间来处理它。
The references to .NET are extremly sparse in there and mainly list the apropriate pieces of the .NET technology stack for a given ara. e.g. Windows Mobile Something for implementing the client of a mobile application. In many cases this is really just marketing.
那里对 .NET 的引用非常稀少，主要列出了给定 ara 的 .NET 技术堆栈的适当部分。例如 Windows Mobile 用于实现移动应用程序客户端的东西。在许多情况下，这实际上只是营销。
So the equivalent for Java would be to recommend the matching Sun solution. Like MySQL for a database. While this approach makes sense for MS, which would prefer their developers to be locked into MS stuff, it does not make sense for Sun/Java which have openess as the major selling argument. So a statement like 'use MS SQL Server for this' would turn into use, Oracle, db2, mysql, ms sql server, hsqldb, derby, informix, postrgres or any other database for this ... not very helpfull. So I guess it won't happen.
因此，Java 的等效项是推荐匹配的 Sun 解决方案。就像数据库的 MySQL。虽然这种方法对 MS 有意义，它希望他们的开发人员被锁定在 MS 的东西上，但对于将开放性作为主要销售论点的 Sun/Java 来说却没有意义。因此，诸如“为此使用 MS SQL Server”之类的语句将变为使用 Oracle、db2、mysql、ms sql server、hsqldb、derby、informix、postrgres 或任何其他数据库……对此没有太大帮助。所以我想这不会发生。
