code发电机主场迎战主场迎战的ORM存储过程 [英] Code generators vs. ORMs vs. Stored Procedures

问题描述

在什么领域做的每一个软件架构亮或失败？

In what domains do each of these software architectures shine or fail?

其中的关键要求会提示你选择一个比其他？

Which key requirements would prompt you to choose one over the other?

请假设你有可用的开​​发谁可以做很好的面向对象的code以及良好的数据库开发。

Please assume that you have developers available who can do good object oriented code as well as good database development.

另外，请避免圣战:)所有三种技术各有利弊，我有兴趣在最适合要使用的。

Also, please avoid holy wars :) all three technologies have pros and cons, I'm interested in where is most appropriate to use which.

推荐答案

这些工具的每个人提供了不同的抽象层，带不同观点一起重写的行为。这些架构的选择，所有建筑的选择取决于技术，控制和组织之间的权衡，无论是应用程序本身，并在那里将要部署的环境。

Every one of these tools provides differing layers of abstraction, along with differing points to override behavior. These are architecture choices, and all architectural choices depend on trade-offs between technology, control, and organization, both of the application itself and the environment where it will be deployed.

• 如果你正在处理一种文化，数据库管理员称雄，然后存储为基础的程序的架构会更容易部署。另一方面，它可以是非常难以管理和版本存储过程

• If you're dealing with a culture where DBAs 'rule the roost', then a stored-procedure-based architecture will be easier to deploy. On the other hand, it can be very difficult to manage and version stored procedures.

code发电机亮当您使用静态类型语言中，因为你可以在编译的时候，而不是在运行时捕获错误。

Code generators shine when you use statically-typed languages, because you can catch errors at compile-time instead of at run-time.

奥姆斯是理想的集成工具，您可能需要处理与安装到安装根据不同的RDBMS中和模式。换一个地图，你的应用程序与PeopleSoft甲骨文合作，与Microsoft Dynamics SQL Server上的工作去。

ORMs are ideal for integration tools, where you may need to deal with different RDBMSes and schemas on an installation-to-installation basis. Change one map and your application goes from working with PeopleSoft on Oracle to working with Microsoft Dynamics on SQL Server.

我在哪里见过产生code用于与存储过程接口的应用，因为存储过程可以被调整，以解决限制在code发生器。

I've seen applications where Generated Code is used to interface with Stored Procedures, because the stored procedures could be tweaked to get around limitations in the code generator.

最终唯一正确的答案将取决于你试图解决的问题并在解决方案需要执行的环境。还有什么是争论的土豆的正确发音。

Ultimately the only correct answer will depend upon the problem you're trying to solve and the environment where the solution needs to execute. Anything else is arguing the correct pronunciation of 'potato'.

这篇关于code发电机主场迎战主场迎战的ORM存储过程的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！