一个系统可以包含多于一个架构风格。
A given system may exhibit more than one architectural style. As Shaw and Garlan describe it.
SOA这种架构风格本质上有五点约束。
SOA is an architectural style with essentially five constraints.
这些架构风格是不同的，它们各有所长。
These architectural styles are different, each with its own unique advantages.
而SOA架构风格最独具一格的特点是。
And the most distinctive features of the SOA architectural style are.
逻辑和技术的架构经验都是整个架构风格的一部分。
Both logical and technical architecture expertise is part of the overall architectural style.
SOA是一种架构风格。
而是由服务器端web应用程序架构风格所产生的问题。
Rather, they are specifically caused by the server-side Web application architectural style.
我还将详述一些在使用SOA架构风格时应该避免的缺陷。
I will also detail some of the pitfalls one should avoid in using an SOA architectural style.
下图说明用于管理安全策略的一种操作策略实施架构风格。
An illustration of an operational policy enforcement architectural style for managing security policy is shown in the figure below.
这些架构风格在系统灵活性和优化上有各自不同的总体目标。
These architectural styles have different overall goals for system flexibility and optimization.
该模型基于已完成的、采用同一类架构风格的项目中获得知识。
The model is based on knowledge captured from already-completed projects that employed the architectural style in that genre.
MDD项目所采用的架构风格是受很多因素影响的，它们包括。
The architectural style adopted by an MDD project can be influenced by a number of factors, including.
更具体的，架构风格定义了组件和连接型的语法，和连接的方法。
More specifically, an architectural style defines a vocabulary of components and connector types, and a set of constraints on how they can be combined. 9.
Ajax架构风格的另外一个优点是它可以轻松处理服务器的故障。
Another benefit of the Ajax architectural style is the ability to deal easily with server failure.
如果多个项目采用相同的架构风格，那么问题发生的假设很有可能成立。
If multiple projects employ the same architectural style, the assumption that issues recur will likely hold.
但是Ajax架构风格使开发人员可以将处理和状态需求分布到客户机。
But the Ajax architectural style lets developers distribute processing and state requirements to the client.
SOA是一种架构风格，它的目标是实现相互交互的软件代理之间的松散耦合。
SOA is an architectural style whose goal is to achieve loose coupling among interacting software agents. 3.
在过去的10年间，IT界在理解和改进这种架构风格上已经取得了显著的进步。
In the last decade, it industry has made tremendous advances in understanding and improving this architecture style.
面向服务架构是一种架构风格，其目的是使用交付业务价值的服务来实现业务机动性。
Service Oriented Architecture is an architectural style that is a means to achieve business agility using services that deliver business value.
我们的灵感来自于REST的架构风格，以及把XML移到HTTP协议之上的能力。
We take our inspiration from the REST architectural style, and the ability to move XML over HTTP.
应用的服务似乎仅使用到了SOA技术，而非架构风格，相反企业服务则让应用淘汰。
It seems like services for applications will leverage only SOA technologies, not SOA architectural style, while services for enterprise seem to make application obsolete.
当我们利用SOA架构风格重铸企业IT环境时所面临的首要问题之一是企业而不是软件。
One of the first issues we face in recasting an enterprise it environment using an SOA architectural style is that the enterprise is not just about software.
提倡将向业务看齐的企业服务作为设计、构建、组合企业业务解决方案基本单元的架构风格。
An architectural style promoting the concept of business-aligned enterprise service as the fundamental unit of designing, building, and composing enterprise business solutions.
呈现和数据绑定的位置看起来可能是一个实现细节，但是这种区别会导致完全不同的架构风格。
The location of presentation and data binding might seem like an implementation detail, but this difference leads to completely different architectural styles.
ROA和EDA是另一种架构风格，“资源”和“事件”分别是其主要的设计驱动力。
ROA and EDA are other architectural styles that have 'resources' or' events' respectively as their primary design driver.
SOA不过是一种构建应用程序的架构风格，促进了组件之间的松散耦合从而更便于组件的重用。
SOA is simply an architectural style for building applications that promotes the loose coupling between components so that you can easily reuse them.
特定的方法定义[...]对REST架构风格没有影响，所以对它们进行风格讨论非常困难。
Specific method definitions […] simply don’t matter to the REST architectural style, so it is difficult to have a style discussion about them.
您了解了有关REST架构风格的特性和概念以及如何使用它与CXF开发RESTful服务。
You learned about the features and concepts of the REST architectural style and how to use it with CXF to develop RESTful services.
在传输服务组合之上，结合REST和其它架构风格来提升Internet上服务集成的效率。
Combine REST with other architectural styles, over a combination of transports for improving Internet service integration efficiency.
是否有必要在其他层中对职责编码主要取决于在用例实现会议中做出的系统架构风格和设计的决策。
Whether it is necessary to code responsibilities in other layers will be driven mainly by the system's architectural style and design decisions made during the use-case realization session.
应用推荐