你在哪里划清设计和建筑之间的界限? [英] Where do you draw the line between design and architecture?

问题描述

敏捷架构问题让我感到疑惑.

这是否取决于正在构建的内容?做申请(我的意思是单身计算程序在这里)有一个架构?

Does it depends of what is being build ? Do applications (I mean single computing program here) have an architecture ?

更新:为了澄清这个问题，我将就这个问题发表我的看法:我将架构定义为系统在组件中的切割，以及组件之间的关系；而设计是关于实习生的组件.这个观点是共享的吗?

UPDATE: to try to clarify the question, I'll give my opinion on the question: I defined the architecture as the cutting of the system in components, and the relationships between the components ;while the design is about the interns of the component. Is this opinion shared ?

推荐答案

这真的相当简单:架构是关于您为满足非功能性"需求而做出的设计决策:成本、可维护性、性能、可靠性、可用性和安全性.这是关于 Web 应用程序的:您可以以无数种方式构建它，从作为 CGI 运行的大型 C 程序(实际上，我们曾经这样做)、Python Web 应用程序，到 J2EE 应用程序，再到 LAMP 应用程序.它们中的任何一个都具有相同的功能行为，它们都将发布相同的页面；当您尝试更改 C 程序的数据库或对大型 LAMP 应用程序进行负载平衡时，就会出现差异.

It's really fairly simple: architecture is about the design decision you make to meet the "non-functional" requirements: requirements like cost, maintainability, performance, reliability, availability, and security. This about a web application: you can build it in a zillion ways, from a big C program that runs as a CGI (really, we used to do that), a Python webapp, to a J2EE application, to a LAMP application. Any of them would have the same functional behavior, they all would post the same pages; the differences come in when you try to change the C program's database or load-balance your big LAMP application.

这篇关于你在哪里划清设计和建筑之间的界限?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！