| Api node ([details](#api-node)) | Handle api calls | no | all | 128 MB | no |
| Api node ([details](#api-node)) | Handle api calls | no | all except account_history | 128 MB | no |
| Raw node ([details](#raw-node)) | _Unconfigured_ | no | account_by_key,<br>condenser | 54 GB | yes |
| Full Api node ([details](#full-api-node)) | Handle api calls | no | all | 128 MB | no |
| Raw node ([details](#raw-node)) | _Unconfigured_ | no | account_by_key | 54 GB | yes |
### Base test node
### Base test node
Nodes are organized in a hierarchy. Init, witness and api nodes are nodes configured for tests. It is described in diagram below as base test node. You can't create this type of node. But all mentioned nodes have same behavior and extend it.
Nodes are organized in a hierarchy. Init, witness, api and full api nodes are nodes configured for tests. It is described in diagram below as base test node. You can't create this type of node. But all mentioned nodes have same behavior and extend it.
Node with default, unmodified configuration. Can be useful for tests which checks default behavior of node. Using this type of node is not recomended. Should be avoided and used only if any other can't meet the requirements. Every raw node creates 54 GB file for block log and has only few APIs included (it means additional code for including APIs in every test case).
Node with default, unmodified configuration. Can be useful for tests which checks default behavior of node. Using this type of node is not recomended. Should be avoided and used only if any other can't meet the requirements. Every raw node creates 54 GB file for block log and has only few APIs included (it means additional code for including APIs in every test case).