优快云 记录学习第一篇

SOA：面向服务编程
面向服务的架构(SOA)是一个组件模型，它将应用程序的不同功能单元(称为服务)进行拆分，并通过这些服务之间定义良好的接口和契约联系起来。接口是采用中立的方式进行定义的，它应该独立于实现服务的硬件平台、操作系统和编程语言。这使得构建在各种各样的系统中的服务可以以一种统一和通用的方式进行交互。(介绍链接：https://baike.so.com/doc/5399617-7584548.html)

WSO2 Carbon Documentation 学习：

Architecture
Carbon Kernel is a modular, light-weight, OSGi-based server development framework, which provides the base for developing servers. Eclipse Equinox is used as the OSGi runtime from Kernel 5.0.0 onwards. However, you can plug in any OSGi implementation to your Carbon server. The diagram below depicts the architecture of WSO2 Carbon Kernel and its key components.（Carbon Kernel是一个模块化，轻量级，基于OSGi的服务器开发框架，为开发服务器提供了基础。 Eclipse Equinox从Kernel 5.0.0开始用作OSGi运行时。 但是，您可以将任何OSGi实现插入Carbon服务器。 下图描绘了WSO2碳核的架构及其关键组件。）
Listed below are the key components that constitute Carbon Kernel 5.1.0:（下面列出了构成Carbon Kernel 5.1.0的关键组件：）

Carbon Launcher
Logging Framework with Log4j 2.0 as the backend
Component Startup Order Resolver
Transport Management
Pluggable Runtime Management（碳发射器
使用Log4j 2.0作为后端的Logging Framework
组件启动顺序解析程序
运输管理
可插拔运行时管理）
Carbon Launcher
The Carbon launcher boots up the Carbon server. This Launcher component implementation resolves the initialization of the Carbon server instance: Before starting the Carbon server, the launcher component performs a set of steps that loads the initial startup configurations. Read about how the Carbon Launcher is used for development.（碳发射器
Carbon发射器启动Carbon服务器。 此Launcher组件实现解决了Carbon服务器实例的初始化：在启动Carbon服务器之前，启动程序组件执行一组加载初始启动配置的步骤。 了解Carbon Launcher如何用于开发。）
Logging Framework with Log4j 2.0 as the backend
The Carbon logging framework is implemented using the PaxLogging framework, which is a well known open-source project that implements strong backend functionalities for logging inside the Carbon server. High performing Log4j 2.0 is used as the logging backend with this framework. For more information on the supported logging API’s and configurations, see Configuring the Logging Framework.（使用Log4j 2.0作为后端的Logging Framework
Carbon日志框架是使用PaxLogging框架实现的，PaxLogging框架是一个众所周知的开源项目，它实现了强大的后端功能，可以在Carbon服务器内部进行日志记录。 高性能Log4j 2.0用作此框架的日志记录后端。 有关支持的日志记录API和配置的更多信息，请参阅配置日志记录框架。）
Component Startup Order Resolver
The Carbon startup order resolver implementation resolves the startup order among multiple components. It also notifies a component when all of its dependencies (OSGi services, OSGi bundle, etc) are available. This implementation leverages some of the OSGi constructs, such as Require-Capability and Provider-Capability manifest header entries, to resolve the ordering among components. Read more about the Startup Order Resolver Framework.（组件启动顺序解析程序
Carbon启动顺序解析器实现解决了多个组件之间的启动顺序。 它还会在组件的所有依赖项（OSGi服务，OSGi包等）可用时通知组件。 此实现利用一些OSGi构造（例如Require-Capability和Provider-Capability清单头条目）来解析组件之间的排序。 阅读有关启动顺序解析器框架的更多信息。）
Transport Management
The Carbon transport management feature provides a pluggable extension point, which allows users to add new transports to the existing server. It also manages the lifecycle of all the transports. Read more about transport management.（运输管理
Carbon传输管理功能提供了一个可插拔的扩展点，允许用户将新传输添加到现有服务器。 它还管理所有传输的生命周期。 详细了解运输管理。）
Pluggable Runtime Management
The pluggable runtime framework in Carbon can be used to manage third-party runtimes in the Carbon server. This framework provides a good deal of flexibility when managing the lifecycle of a runtime. This is useful in situations where it is necessary to use the server in maintenance mode etc. In this case, each runtime needs to be set to maintenance mode. WSO2 Carbon will use this extension point to trigger a lifecycle change to enable the maintenance mode of the runtime. For example, in case of the Tomcat runtime, you need to stop the Tomcat connectors when the server goes into maintenance mode. Read more about pluggable runtime management.（可插拔运行时管理
Carbon中的可插入运行时框架可用于管理Carbon服务器中的第三方运行时。 在管理运行时的生命周期时，此框架提供了很大的灵活性。 这在需要在维护模式等中使用服务器的情况下非常有用。在这种情况下，需要将每个运行时设置为维护模式。 WSO2 Carbon将使用此扩展点触发生命周期更改以启用运行时的维护模式。 例如，对于Tomcat运行时，您需要在服务器进入维护模式时停止Tomcat连接器。 阅读有关可插入运行时管理的更多信息。）