Skip to content

Commit c6b8c4f

Browse files
Mohsin ZaidiMohsin Zaidi
authored andcommitted
remove PostgreSQL references from technical requirements
1 parent 1f63cd9 commit c6b8c4f

1 file changed

Lines changed: 7 additions & 74 deletions

File tree

docs/introduction/technical-reqs.md

Lines changed: 7 additions & 74 deletions
Original file line numberDiff line numberDiff line change
@@ -6,24 +6,16 @@ Ceramic is a decentralized data storage network made up of different components,
66

77
![Architecture](/img/app-architecture-overview.png)
88

9-
10-
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-
129
When integrating with Ceramic, you will be running a few different services and components, each serving a specific purpose for running your application:
1310

1411
- `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
1612
- `EVM RPC node access` - required for self-anchoring to EVM blockchains (optional, but recommended for production)
1713

1814
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.
1915

20-
Ceramic nodes are simply pieces of software that run on a server. PostgreSQL is a type of traditional database.
21-
2216
## Hardware requirements
2317

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.
2719

2820
### Minimum (light throughput)
2921

@@ -33,8 +25,6 @@ Depending on the expected throughput of your project, the suggested hardware req
3325
| RAM | 4GB |
3426
| Storage | 110GB |
3527

36-
37-
3828
### Recommended
3929

4030
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.
4535
| RAM | 8 GB |
4636
| Storage | 180GB |
4737

48-
4938
### Advanced (heavy throughput)
5039

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.
52-
53-
54-
55-
<div style={{ display: "flex", justifyContent: "flex-start" }}>
56-
<div style={{ marginRight: "100px" }}>
57-
<div style={{ fontWeight: "bold", marginBottom: "8px" }}>Ceramic node</div>
58-
<table style={{ borderCollapse: "collapse", width: "100%" }}>
59-
<thead>
60-
<tr>
61-
<th style={{ textAlign: "left", padding: "8px" }}>Resource</th>
62-
<th style={{ textAlign: "left", padding: "8px" }}>Size</th>
63-
</tr>
64-
</thead>
65-
<tbody>
66-
<tr>
67-
<td style={{ textAlign: "left", padding: "8px" }}>CPU</td>
68-
<td style={{ textAlign: "left", padding: "8px" }}>2 4CPU Cores</td>
69-
</tr>
70-
<tr>
71-
<td style={{ textAlign: "left", padding: "8px" }}>RAM</td>
72-
<td style={{ textAlign: "left", padding: "8px" }}>8 GB</td>
73-
</tr>
74-
<tr>
75-
<td style={{ textAlign: "left", padding: "8px" }}>Storage</td>
76-
<td style={{ textAlign: "left", padding: "8px" }}>180GB</td>
77-
</tr>
78-
</tbody>
79-
</table>
80-
</div>
81-
82-
<div>
83-
<div style={{ fontWeight: "bold", marginBottom: "8px" }}>PostgreSQL DB</div>
84-
<table style={{ borderCollapse: "collapse", width: "100%" }}>
85-
<thead>
86-
<tr>
87-
<th style={{ textAlign: "left", padding: "8px" }}>Resource</th>
88-
<th style={{ textAlign: "left", padding: "8px" }}>Size</th>
89-
</tr>
90-
</thead>
91-
<tbody>
92-
<tr>
93-
<td style={{ textAlign: "left", padding: "8px" }}>CPU</td>
94-
<td style={{ textAlign: "left", padding: "8px" }}>1 2CPU Cores</td>
95-
</tr>
96-
<tr>
97-
<td style={{ textAlign: "left", padding: "8px" }}>RAM</td>
98-
<td style={{ textAlign: "left", padding: "8px" }}>4 GB</td>
99-
</tr>
100-
<tr>
101-
<td style={{ textAlign: "left", padding: "8px" }}>Storage</td>
102-
<td style={{ textAlign: "left", padding: "8px" }}>110GB</td>
103-
</tr>
104-
</tbody>
105-
</table>
106-
</div>
107-
</div>
108-
109-
40+
| Resource | Size |
41+
| --- | --- |
42+
| CPU | 4 CPU Cores |
43+
| RAM | 8 GB |
44+
| Storage | 180GB+ |
11045

11146
## Hosting solutions and costs
11247

113-
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.
11449

11550
<table style={{ width: "100%", borderCollapse: "collapse" }}>
11651
<tr>
@@ -134,5 +69,3 @@ One of the key factors impacting costs is how you choose to host your Ceramic no
13469
<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>
13570
</tr>
13671
</table>
137-
138-

0 commit comments

Comments
 (0)