事件架构非同步模式是另一个选项。
需要得到事件通知的用户和管理员可以利用此架构并从中受益。
Users or administrators that need such event notifications can utilize this framework and benefit from it.
正如我们已经看到的，一旦我们能从正常工作中分离变化，架构就能只依赖事件和生命周期进行设计和实现。
As we have seen earlier, once we are able to separate normal operations from changes, the architecture can rely solely on events and lifecycles for design and implementation.
如果没有完善设计的安全性事件收集和分析架构，存储、检索和理解这样巨大的信息量是非常困难的。
The sheer amount of data makes the storage, retrieval, and understanding of this information very difficult without a properly designed security event gathering and analysis architecture.
面向服务的架构可以是事件驱动的，也可以不是——我个人并不认为EDA是不同的架构风格，而把它看做面向服务的一个方面。
Service oriented architectures can be event driven or not - I do not personally see EDA as a different architectural style, rather perceive it as simply one aspect of service orientation.
对技术人员来说，动态模型被翻译成一个匹配各种事件、生命周期和变化类型的插件架构。
For technologists, the dynamic model translates into a plug-in architecture that matches various events, lifecycles, and types of changes.
前者将使得使用SCA创建基于事件的架构成为可能，而且将复杂的事件处理集成到应用中也会更加简便。
The former will make it possible to create event-based architectures using SCA as well as more easily incorporate complex event processing into their applications.
下面这一节将讨论一种更健壮的、全面的用于重复事件的架构。
The next section will cover a more robust, comprehensive architecture for repeating events.
问题与事件管理系统，以及问题判定与检修工具，应在架构的各个层次提供充足的可配置的信息。
Problem and incident management systems along with problem determination and troubleshooting utilities should provide a sufficient configurable level of information at all levels of your architecture.
在CIM架构中，客户机应用程序可以订阅CIM事件的通知。
In the CIM architecture, a client application can subscribe to be notified of CIM events.
在EDA内部，您可以跨soa的各个分段(包括物理层和架构的虚拟层)传输事件，这样系统可以有效地作出响应。
Within an EDA, you can transmit events across all segments of an SOA, including physical tiers and an architecture's virtual layers, so that systems respond and act effectively.
也许，他们还想利用这次事件重新考虑他们公司的内部架构。
But they might want to use the incident to reconsider their own internal workings, too.
图1说明了跨架构堆栈各层传播的事件。
Figure 1 illustrates events propagated across layers of an architectural stack.
我想了解的是，它将如何发挥作为事件驱动架构基础的作用，以及如何与之协同工作。
What I'm looking at is how it can serve as the foundation for an Event-Driven Architecture, work in tandem with that.
即使根本没有发生并行操作，事件驱动的异步架构也提供了优于传统同步设计的强大的可伸缩性。
Asynchronous, event-driven architectures also have a massive scalability advantage over traditional synchronous designs, even if no parallel operations occur at all.
当事件发布者与事件接收者位于架构虚拟层中的同一层时，发生水平因果关系。
Horizontal causality occurs when the event publisher resides on the same layer in an architecture's virtual layers as the event receiver.
根据应用程序的架构，可能触发其他事件，并且可能不需要获取Onselect事件。
Depending on your application architecture, other events might be triggered, and you might not necessarily get the Onselect event.
他感兴趣的领域包括SpringFramework、领域驱动设计、事件驱动架构以及面向方面的编程。
He is mostly interested in Spring framework, Domain Driven Design, Event Driven Architecture and Aspect Oriented Programming.
OASISWebServicesNotification (WS-N)规范（参见 [3][4][5]）通常在事件驱动架构中用作通知标准。
The OASIS Web Services Notification (WS-N) specification (see [3][4][5]) is commonly used as a notification standard in an event driven architecture.
事件发布中有三种类型的消息，如上面事件发布架构的图中所示
There are three types of messages in event publishing, as shown in above in the figure Event publishing architecture
尽管本文并没有考虑分发系统，但是也展示了一些可以构建在其上的公共事件基础架构的配置功能。
Although this article does not consider distributed systems, it demonstrates some of the configuration capabilities of the Common Event Infrastructure that can be built upon.
本文概述了公共事件基础架构从技术预览版到产品发布版的变更和新增的功能。
This article provides an overview of the changes and added functionality of the Common Event Infrastructure from technical preview to production release.
在这个示例中，我们假定这样一个事件驱动架构：异步消息(或通知)通过消息或通知代理在系统的组件之间交换。
In this example, we assume an event-driven architecture where asynchronous messages, or notifications, are exchanged among the components of the system by means of a message or notification broker.
当一个或多个关键架构要素的行为是事件驱动时，用状态图建模可以对理解该行为特别有用。
When the behavior of one or more key architectural elements is event-driven, modeling with State Diagrams can be especially useful in understanding that behavior.
在开始使用事件基础架构之前，首先应该熟悉事件和发射器的概念。
Before you begin to work with the event infrastructure, you need to familiarize yourself with the concepts of events and emitters.
在事件处理架构中经常采用回调，这样您指定的代码将在稍后调用。
Callbacks are frequently used in event handling architectures, where you designate code to be invoked at a later time.
首先创建一个简单的事件数据库架构，类似于清单2中的架构。
First, create a simple database schema for events like the schema shown in Listing 2.
如果事件基础架构发生故障，那么可能导致客户端事务打上回滚标记(依赖于故障的种类)。
If the event infrastructure fails, then this may cause the client's transaction to be marked for rollback (depending on the nature of the failure).
本文也让期望使用公共事件基础架构的人对其有大致的了解。
It also provides an overview for anyone looking to use the Common Event Infrastructure.
ESB支持这些服务交互功能，并提供集成的通信、消息传递以及事件基础架构来支持这些功能。
The ESB supports these service interaction capabilities, and provides the integrated communication, messaging, and event infrastructure to enable them.
应用推荐