You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To make it easier to grasp, you can think about implementing Ceramic just like you might think about implementing a traditional SQL or PostgreSQL database.
11
-
12
9
When integrating with Ceramic, you will be running a few different services and components, each serving a specific purpose for running your application:
13
10
14
11
-`ceramic-one` - the Ceramic node written in Rust, responsible for storing data, providing HTTP API access, and coordinating with network participants
15
-
-`PostgreSQL` - used for indexing data
16
12
-`EVM RPC node access` - required for self-anchoring to EVM blockchains (optional, but recommended for production)
17
13
18
14
With self-anchoring support, you can run your own anchor service on any EVM-compatible blockchain instead of relying on external services. See [Self-Anchoring](../protocol/ceramic-one/anchoring/overview) for more details.
19
15
20
-
Ceramic nodes are simply pieces of software that run on a server. PostgreSQL is a type of traditional database.
21
-
22
16
## Hardware requirements
23
17
24
-
For most projects, all three components of Ceramic can be run on the same server. Thus the main consideration impacting costs are the hardware requirements of your server.
25
-
26
-
Depending on the expected throughput of your project, the suggested hardware requirements will differ. Below, you can find the estimated hardware requirements based on a different levels of expected throughput.
18
+
Depending on the expected throughput of your project, the suggested hardware requirements will differ. Below, you can find the estimated hardware requirements based on different levels of expected throughput.
27
19
28
20
### Minimum (light throughput)
29
21
@@ -33,8 +25,6 @@ Depending on the expected throughput of your project, the suggested hardware req
33
25
| RAM | 4GB |
34
26
| Storage | 110GB |
35
27
36
-
37
-
38
28
### Recommended
39
29
40
30
As your project scales, you may need to expand your storage beyond 180GB.
@@ -45,72 +35,17 @@ As your project scales, you may need to expand your storage beyond 180GB.
45
35
| RAM | 8 GB |
46
36
| Storage | 180GB |
47
37
48
-
49
38
### Advanced (heavy throughput)
50
39
51
-
Advanced users may want to consider running the PostgreSQL database on a different server than the Ceramic node. If you choose to run them on different servers, a VPC can be used to establish the communication between them.
One of the key factors impacting costs is how you choose to host your Ceramic node. A few options are shown below. Monthly server costs are **estimated** based on the hardware requirements above.
48
+
One of the key factors impacting costs is how you choose to host your Ceramic node. A few options are shown below. Monthly server costs are **estimated** based on the hardware requirements above.
@@ -134,5 +69,3 @@ One of the key factors impacting costs is how you choose to host your Ceramic no
134
69
<td style={{ textAlign: "left", verticalAlign: "top" }}>- Application developers who prefer to use third party managed node services can offload node management responsibilities to dedicated professionals</td>
0 commit comments