Getting Started with Oracle Blockchain Platform Enterprise Edition for Hyperledger Besu
This topic describes the infrastructure requirements, resources, and components needed for an instance.
Supported Compute Shapes
The following compute shapes are supported for Oracle Blockchain Platform Enterprise Edition for Hyperledger Besu:
| Compute Shape |
|---|
| VM.Standard.E3.Flex |
| VM.Standard.E4.Flex |
| VM.Standard.E5.Flex |
For more information on Flex Shapes, see Flexible Shapes.
Resource Estimates
The following table provides details on the minimum service and resource configuration used by Oracle Blockchain Platform Enterprise Edition for Hyperledger Besu. Ensure that these are available in your tenancy or the stack creation will fail.
| Service or Resource | Estimated Base Usage |
|---|---|
| Oracle Kubernetes Engine (OKE) | 1 OKE cluster |
| OKE Node Pool | 1
Note: If you're manually creating the stack, the OKE node pool must be set to 39 pods per node. If a new node pool is being created for additional instances, ensure it is set to 14 pods per node minimum. |
| Compute Instances | 1 instance, used by the jump host |
| Bastion Service | 1, used for the jump host connection |
| Container Registry (OCIR) | 10
This is used to store container images for Oracle Blockchain Platform Enterprise Edition components. Ensure 8GB of space is available. |
| Virtual Cloud Network (VCN) | 1 VCN, used by the cluster and jump host |
| Load Balancer and IP Addresses | 2 or more, 1 for Blockchain Platform Manager, 1 for each Besu instance |
Cluster Requirement for Hyperledger Besu
Each instance requires a minimum of 1 worker node.
| Number of Instances | Worker Node Count | Worker Node Configuration | Worker Node Boot Volume | Load Balancer/IP Address Count |
|---|---|---|---|---|
| 1 | 1 |
4 OCPU 64GB memory |
150GB | 2 total
|
| 2 | 2 |
4 OCPU 64GB memory |
150GB | 3 total
|
Instance Components
A deployed instance of the Besu network provides the following node components.
| Component | Default | Minimum | Maximum | Description |
|---|---|---|---|---|
| Validator nodes | 4 | 4 | 7 | Hyperledger Besu nodes that propose, validate, and add blocks of transactions to the ledger. They use the Quorum Byzantine Fault Tolerance (QBFT) consensus protocol to agree on each block before it is added. |
| Boot nodes | 2 | 1 | 2 | Boot nodes act as initial connection points, so that new or restarting nodes can discover the network. |
| RPC nodes | 2 | 1 | 3 | Hyperledger Besu nodes that expose the Ethereum JSON-RPC (JavaScript Object Notation Remote Procedure Call) APIs. They let applications and tools read blockchain data and submit transactions without running their own node. |
The instance includes managed components such as an RPC Proxy, a console, wallet storage, and related infrastructure, providing a complete environment to perform lifecycle management (LCM) operations, manage the instance’s network, and submit transactions through the RPC Proxy.
| Component | Description |
|---|---|
| RPC proxies | Oracle services that are used to authenticate, manage, and scale access to Web3 JSON-RPC APIs. |
| Service consoles | Oracle services that let you administer a Besu network through a web console or APIs. A user's access depends on their assigned role and privileges. |
| Wallet service | An Oracle custodial wallet service that can register and manage user key pairs, sign user transactions, and send transactions to the Besu network for processing. |