BAETYL 1.0.0 Documentation
Welcome to BAETYL’s documentation! [https://baetyl.io/en/] Baetyl, extend cloud computing, data and service seamlessly to edge devices. BAETYL Home [https://baetyl.io/en/] Overview What is Baetyl Baetyl connect to Hub Service Message transferring among devices with Hub Service Message handling with Function Service Message Synchronize between baetyl-hub and Baidu IoTHub via Remote Service Image capturing capturing and AI model inference with Video infer Service Development How to write a python script for Python runtime How to write a javascript for Node runtime How to import third-party libraries for Python0 码力 | 135 页 | 15.44 MB | 1 年前3BAETYL 0.1.6 Documentation
Welcome to BAETYL’s documentation! [https://baetyl.io/en/] Baetyl, extend cloud computing, data and service seamlessly to edge devices. BAETYL Home [https://baetyl.io/en/] Overview What is Baetyl Advantages Baetyl with Hub service Workflow Connection Test Message transferring among devices with Local Hub Service Workflow Message Routing Test Message handling with Local Function Service Workflow Message framework of Linux Foundation Edge [https://www.lfedge.org] that extends cloud computing, data and service seamlessly to edge devices. It can provide temporary offline, low-latency computing services, and0 码力 | 119 页 | 11.46 MB | 1 年前3Hyperledger Fabric 2.1 Documentation
modular components: A pluggable ordering service establishes consensus on the order of transactions and then broadcasts blocks to peers. A pluggable membership service provider is responsible for associating network with cryptographic identities. An optional peer-to-peer gossip service disseminates the blocks output by ordering service to other peers. Smart contracts (“chaincode”) run within a container environment decoupled from the peers that execute transactions and maintain the ledger. Specifically, the ordering service. Since consensus is modular, its implementation can be tailored to the trust assumption of a particular0 码力 | 904 页 | 10.95 MB | 1 年前3Hyperledger Fabric 1.4.8 Documentation
modular components: A pluggable ordering service establishes consensus on the order of transactions and then broadcasts blocks to peers. A pluggable membership service provider is responsible for associating network with cryptographic identities. An optional peer-to-peer gossip service disseminates the blocks output by ordering service to other peers. Smart contracts (“chaincode”) run within a container environment decoupled from the peers that execute transactions and maintain the ledger. Specifically, the ordering service. Since consensus is modular, its implementation can be tailored to the trust assumption of a particular0 码力 | 699 页 | 9.02 MB | 1 年前3Hyperledger Fabric 1.4.9 Documentation
modular components: A pluggable ordering service establishes consensus on the order of transactions and then broadcasts blocks to peers. A pluggable membership service provider is responsible for associating network with cryptographic identities. An optional peer-to-peer gossip service disseminates the blocks output by ordering service to other peers. Smart contracts (“chaincode”) run within a container environment decoupled from the peers that execute transactions and maintain the ledger. Specifically, the ordering service. Since consensus is modular, its implementation can be tailored to the trust assumption of a particular0 码力 | 701 页 | 9.02 MB | 1 年前3Hyperledger Fabric 1.4 Documentation
modular components: A pluggable ordering service establishes consensus on the order of transactions and then broadcasts blocks to peers. A pluggable membership service provider is responsible for associating network with cryptographic identities. An optional peer-to-peer gossip service disseminates the blocks output by ordering service to other peers. Smart contracts (“chaincode”) run within a container environment decoupled from the peers that execute transactions and maintain the ledger. Specifically, the ordering service. Since consensus is modular, its implementation can be tailored to the trust assumption of a particular0 码力 | 701 页 | 9.02 MB | 1 年前3Cilium v1.10 Documentation
Hubble can answer questions such as: Service dependencies & communication map What services are communicating with each other? How frequently? What does the service dependency graph look like? What HTTP HTTP calls are being made? What Kafka topics does a service consume from or produce to? Network monitoring & alerting Is any network communication failing? Why is communication failing? Is it DNS? Is it requests? Application monitoring What is the rate of 5xx or 4xx HTTP response codes for a particular service or across all clusters? What is the 95th and 99th percentile latency between HTTP requests and responses0 码力 | 1307 页 | 19.26 MB | 1 年前3Cilium v1.9 Documentation
Hubble can answer questions such as: Service dependencies & communication map What services are communicating with each other? How frequently? What does the service dependency graph look like? What HTTP HTTP calls are being made? What Kafka topics does a service consume from or produce to? Network monitoring & alerting Is any network communication failing? Why is communication failing? Is it DNS? Is it requests? Application monitoring What is the rate of 5xx or 4xx HTTP response codes for a particular service or across all clusters? What is the 95th and 99th percentile latency between HTTP requests and responses0 码力 | 1263 页 | 18.62 MB | 1 年前3Cilium v1.11 Documentation
Hubble can answer questions such as: Service dependencies & communication map What services are communicating with each other? How frequently? What does the service dependency graph look like? What HTTP HTTP calls are being made? What Kafka topics does a service consume from or produce to? Network monitoring & alerting Is any network communication failing? Why is communication failing? Is it DNS? Is it requests? Application monitoring What is the rate of 5xx or 4xx HTTP response codes for a particular service or across all clusters? What is the 95th and 99th percentile latency between HTTP requests and responses0 码力 | 1373 页 | 19.37 MB | 1 年前3Hyperledger Fabric 2.2.1 Documentation
modular components: A pluggable ordering service establishes consensus on the order of transactions and then broadcasts blocks to peers. A pluggable membership service provider is responsible for associating network with cryptographic identities. An optional peer-to-peer gossip service disseminates the blocks output by ordering service to other peers. Smart contracts (“chaincode”) run within a container environment decoupled from the peers that execute transactions and maintain the ledger. Specifically, the ordering service. Since consensus is modular, its implementation can be tailored to the trust assumption of a particular0 码力 | 848 页 | 11.56 MB | 1 年前3
共 573 条
- 1
- 2
- 3
- 4
- 5
- 6
- 58