Camel概念【Architecture ①】

1.4 Camel’s architecture
Let’s now turn our attention to Camel’s architecture. We’ll first take a look at the high-level architecture and then drill down into the specific concepts. After you’ve read this section, you should be caught up on the integration lingo and be ready for chapter 2, where we’ll explore Camel’s routing capabilities.
1.4.1 Architecture from 10,000 feet
We think that architectures are best viewed first from high above(高空俯視). Figure 1.6 shows a high-level view of the main concepts that make up Camel’s architecture.

At a high level, Camel is composed of processors, components, and routes.

All of these are contained within the  CamelContext（他們都被包含在camel上下文中）。

The routing engine uses routes as specifications for where messages are routed.（消息進行路由交換時，路由引擎把routes當作載體）

Routes are defined using one of Camel’s domain-specific languages ( DSL s). （Routes是由一種camel的領域類語言定義的）

Processors are used to transform and manipulate messages during routing and also to implement all the  EIP patterns, which have corresponding keywords in the  DSL languages.（在路由交換過程當中，Processors用於傳輸和處理messages，他也實如今dsl中存在響應關鍵詞的全部的企業集成模式）

 Components are the extension points in Camel for adding connectivity to other systems. To expose these systems to the rest of Camel, components provide an endpoint interface.（Components做爲camel連通其餘系統的拓展節點，爲了使camel框架的其餘部分和這些系統更加融合，Components提供了端點接口）