blocks|key|854418|text|像其他类似的术语一样，这些术语在不同的地方有不同的用法，有时还可以互换。下面是它们之间的典型差异：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|854419|854420|应用程序架构师就是我们中的许多人所说的架构师。负责特定解决方案/项目的最高设计级别和范围的人员。如果周围有其他类型的架构师，你会在标题中使用应用程序，并且你想清楚地表明，这个人主要关心特定的应用程序。企业架构师|unordered-list-item|offset|length|style|BOLD|854421|担心的是所有的公司解决方案。它们如何相互依赖，如何相互使用，它们共同的维护和改进的效率如何。他思考所有的解决方案如何共同支持公司的使命。只有更大的公司才有资格获得这个宏伟的头衔。企业架构师是会见首席信息官、首席技术官和其他类似大人物的大人物。|854422|系统架构师可能被认为比应用程序架构师的范围更广，而且比企业架构师的范围更小。这个头衔有时与应用程序架构师完全相同-特定项目的大人物。有时，标题中的系统部分可以注意到更广泛的范围:职责包括软件但也包括硬件和IT的人，或者担心多个项目的人。|854423|854424|entityMap^0|0|0|0|7|2S|5|0|0|0|5|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|S|8|@$F|T|G|U|H|I]|$F|V|G|W|H|I]]|9|@]|A|$]]|$1|J|3|K|5|E|7|X|8|@]|9|@]|A|$]]|$1|L|3|M|5|E|7|Y|8|@$F|Z|G|10|H|I]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|11|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|P|$]]

Like any other such term, these terms are used differently in different places, and are sometimes interchangeable. Here's what the differences typically are:

<ul>
<li>The Application Architect is is what many of us just call the Architect. The person responsible for the highest levels of design and scope for a particular solution/project. You'd bother using Application in the title if there were other types of architects around, and you wanted it clear that this person worries mainly about a particular application. </li>
<li>The Enterprise Architect is worried
about all of a companies solutions. 
How they rely on each other, how they
use each other, how efficient can
their common upkeep and improvement
be made. He thinks about how all the solutions together support the company's mission. Only a larger company could warrant this grandiose title. The Enterprise Architect is a big shot who meets with the CIO, CTO, and other such big shots.</li>
<li>The Systems Architect might be considered to have a wider scope than the Application Architect, and less than an Enterprise Architect. This title is sometimes the exact same thing as Application Architect - big shot on a particular project. Sometimes the System part of the title cannotes a wider scope: person who duties include software but also hardware and IT, or someone worried about multiple projects.</li>
</ul>

blocks|key|2262898|text|每种方法的真正含义由您工作的公司决定；有些人称之为解决方案架构师，有些人称之为系统架构师。他们都是(假定的)高级职位，对系统/软件设计有一些隐含的监督，但除此之外，我从来没有看到过一个能让每个人都满意的定义。“企业”确实暗示了该职位的一些范围，但它可以说与“系统”没有什么不同(同样，取决于公司)。应用程序架构师通常会让我想到当了一段时间的高级开发人员，HR需要一个新的头衔来奖励绩效。有点像一些大公司高举“副总裁”头衔的方式，它实际上并不意味着你有多少天的假期。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2262899|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|$]]

What each means really is determined by the company you work for; what some call a Solution Architect others call a System Architect. They're all (assumed) senior positions with some implied oversight of system/software design but aside from that I've never seen one definition that will make everyone happy. "Enterprise" does imply some scope to the position, but it's arguably no different than "Systems" (again, depends on the company). Application Architect usually makes me think of someone who's been around as a senior developer for a while and HR needed a new title to reward performance. Sort of like the way some massive companies lob the "Vice President" title around to the point it doesn't really mean anything besides how many vacation days you get.

blocks|key|854515|text|见鬼的..。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|854516|架构师:应用程序-设计应用程序系统-设计多个应用程序并协调成一个系统企业-设计系统并与业务企业的其他非系统方面协调。|854517|让我们不要忘记薪水，奖金，以及你花了多少时间来担心你的头衔。|854518|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|$]]

What the Hell..

Architect:
Application - designs applications
Systems - designs multiple applications and coordinates into a system
Enterprise - designs systems and coordinates with the other non system aspects of the business enterprise.

Let's not forget salary, bonus and how much time you spend on worrying about your title.

blocks|key|2262994|text|嗯，听起来你还在上学，但是放眼商业世界，期待名片上的头衔像学位系统一样结构化……不是的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2262995|实话实说，企业头衔要么是公司特定的职位，以支持内部薪资等级制度，要么是组织结构图。除了非常笼统的条款之外，很难从一家公司转移到另一家公司。它不是一个真正的基准，像学士或博士学位。|2262996|就头衔和工作角色而言，公司中的团队通常分为基础设施(服务器设置和网络)和应用程序(数据库管理员，开发人员)组。不同的公司有很多不同之处，但这似乎是相当普遍的。|2262997|我认为你在计划中最好的办法是决定你喜欢做什么，然后学习把它做好。在此过程中，作为一名IT人员，你必须在所有领域都学到一点东西，才能在任何领域都非常有效。|2262998|祝好运!|2262999|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

Well it sounds like your in school still but looking into the business world and expecting titles on the cards to be as structured as a degree system... its not.

Truth be told the business title is either a company specific job-title to support the internal pay-grade system or the org charts. Its hard to take from one company to another on anything more than very general terms. Its not really a benchmark like a BA or PHD.

As far as titles and job roles go, teams in companies generally break down into Infrastructure (Server setup and networking), and Applications (DB admins, developers) groups. There is a lot of variance by company but that seems to be pretty universal. 

I think your best bet in planning is to decide what you like to do, and then study to do it very well. Along the way as an IT guy you have to pick up a little in all areas to be very effective in any area anyway..

Good luck!

blocks|key|854606|text|多年来，我遇到过许多不同头衔的建筑师，我对他们的角色肯定有自己的看法，然而，不同的公司，甚至不同的国家，其角色也不尽相同。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|854607|企业架构师--负责整个企业的战略思考、路线图、原则和治理。通常与业务、供应商和高级IT管理人员关系密切。|854608|解决方案或系统架构师-在企业架构团队制定的框架内，负责为一组特定的业务需求设计高级解决方案。此解决方案可以跨越多个应用程序。|854609|集成或SOA架构师--负责集成和/或业务服务策略和治理。由于此角色通常跨越整个企业，因此它通常由EA执行，然而，集成架构师通常会在比EA更详细和更技术的级别上工作。在SOA中，集成架构师也可以是卓越中心(或集成能力中心)的成员(甚至是领导者)|854610|信息架构师-负责定义数据模型、主数据管理/所有权解决方案和数据质量流程，以支持整个企业的事务、参考数据和报告系统。通常由EA执行。|854611|应用程序架构师-负责特定应用程序或应用程序套件的实现和流程。所讨论的应用程序可能是定制的现成产品。应该对产品/应用程序有深入的了解，并经常被其他架构师作为更大解决方案的一部分进行咨询|854612|在我的经验中，这些是最常见的标题，但您还会时不时地看到其他架构角色：|854613|854614|技术架构师(对我来说，这与应用程序架构师相同，但其他人可能不同意|unordered-list-item|854615|业务架构师(定义业务策略和processes)|854616|Infrastructure+Architect+(服务器、平台决策，通常还有security)|854617|Network+architect+(显而易见)|854618|854619|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|12|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|13|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|14|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|15|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|16|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|O|3|P|5|Q|7|18|8|@]|9|@]|A|$]]|$1|R|3|S|5|Q|7|19|8|@]|9|@]|A|$]]|$1|T|3|U|5|Q|7|1A|8|@]|9|@]|A|$]]|$1|V|3|W|5|Q|7|1B|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|Z|$]]

I've encountered quite a few architects with varying titles over the years, and I definitely have my own view on the role of each of them, however it does tend to vary from company to company, and even more so from country to country.

Enterprise Architect - responsible for strategic thinking, roadmaps, principles, and governance of the entire enterprise. Usually has a close relationship with the business, vendors, and senior IT management. 

Solutions or Systems Architect - responsible for desiging a high level solution to a specific set of business requirements, within the framework laid down by the enterprise architecture team. This solution may span multiple applications.

Integration or SOA Architect - responsible for the integration and/or business service strategy and governance. Since this role usually spans the entire enterprise it is often performed by an EA, however an integration architect will usually work at a more detailed and technical level than an EA. In a SOA, an integration architect may also be a member (or even leader) of the centre of excellence (or integration competency centre)

Information Architect - responsible for defining data models, master data management / ownership solutions, and data quality processes to support transactional, reference data, and reporting systems throughout the enterprise. Often performed by an EA.

Application Architect - responsible for implementation of, and processes within, a specific application or suite of applications. The application in question may be bespoke of a customised of-the-shelf product. Should have deep knowledge of the product/application and will often be consulted by other architects as part of a larger solution

Those are the most common titles in my experience, but there are other architecture roles that you'll see from time-to-time: 

<ul>
<li>Technical Architect (for me this is the same as an application architect but others may disagree </li>
<li>Business Architect (defines business strategy and processes)</li>
<li>Infrastructure Architect (servers, platform decisions, and often security)</li>
<li>Network Architect (obvious)</li>
</ul>

blocks|key|854644|text|企业架构师是所有角色中最重要的角色。他必须具备完整的技术实现知识。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|854645|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|$]]

Enterprise Architect is biggest role of all. He has to have complete technological implementation knowledge.

So many buzzwords. Not sure if I need to start playing BS Bingo or not. And I'm not trying to be cynical. But I've heard many people with these various titles. There never seems to be a clear delineation between the three. Or there's a lot of domain crossover between the three. Actually, another I've seen while looking around here on Stackoverflow has been "Solutions Architect" as well. But that one doesn't seem to be so prevalent in other places.

There are questions here and there with vague answers. But I'd like definative answers to this. Please assume I'm still relatively new to software stuff and that I'm trying to map out a career path.

Oh, and please be gentle folks; this most definitely is not a duplicate question. Neither is it an aggregate. So kindly leave it alone. Xp

Application Architect vs. Systems Architect vs. Enterprise Architect?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

太多的流行语了。不知道我是否需要开始玩Bingo游戏。我并不是想表现得愤世嫉俗。但我听说过很多人有这些不同的头衔。这三者之间似乎从来没有明确的界限。或者在三者之间存在大量的领域交叉。实际上，我在Stackoverflow上看到的另一个例子是“解决方案架构师”。但这一点在其他地方似乎并不普遍。这里有一些问题，但答案却很模...

问应用程序架构师与系统架构师还是企业架构师？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问应用程序架构师与系统架构师还是企业架构师？EN