README ¶
Flavors
A flavor is a reusable collection of plugins with initialized dependencies.
The most importatnt CN-Infra flavors are:
- local flavor - a minimal set of plugins. It is used to just initialize logging & statuscheck. It is useful for embedding agent plugins into different projects that use their own infrastructure.
- RPC flavor - a collection of plugins that expose RPCs.
It also registers management APIs for:
- status check (RPCs probed from systems such as K8s)
- logging (for changing log level at runtime remotely)
- connectors flavor - is combination of ETCD, Cassandra, Redis & Kafka related plugins.
The following diagram depicts:
- plugins that are parts of a specific flavor
- the initialized (injected) statuscheck dependency within the etcd client plugin and the Kafka client plugin
- the local flavor embedded in:
Documentation ¶
Overview ¶
Package flavors contains predefined cn-infra flavors. A flavor is a re-usable collection of plugins with initialized dependencies. It is typically used as a starting point for developing a cn-infra based app. A flavor contains plugins required by the app. App developers can also define their own flavors or extend one of the predefined flavors.
Directories ¶
Path | Synopsis |
---|---|
Package connectors defines "Connectors" flavor, which is a combination of all plugins that allow connectivity to external database/messaging.
|
Package connectors defines "Connectors" flavor, which is a combination of all plugins that allow connectivity to external database/messaging. |
Package local defines "Local" flavor, which combines logging with StatusCheck.
|
Package local defines "Local" flavor, which combines logging with StatusCheck. |
Package rpc defines "RPC" flavor, which combines all plugins that provide RPC-like access.
|
Package rpc defines "RPC" flavor, which combines all plugins that provide RPC-like access. |
Click to show internal directories.
Click to hide internal directories.