As a top-tier node provider, we love explaining different aspects of crypto node usage. Get ready, make yourself comfortable, and meet a new GetBlock longread about different node types.
So, for various Web3 applications, there are various node demands, and that’s where we start.
Different node types for different tasks
Shared nodes are good for small and medium projects, as they are cheap and easy to manage. As you may suppose, they are shared with other users, saving time and resources. Everyone can select how many computational resources they need—and get them without overpayments, just to run their project.
In contrast, dedicated nodes are personalized, very powerful, and more expensive. They are indispensable when you run a large project, used by thousands of people every day. Only a node owner may access it, while all node administration and management are on our side.
All these nodes are specific types of private nodes. Dedicated nodes are highly optimized for a project and managed by a dedicated (as you may guess) team of DevOps. If you need any of these nodes—just contact us!
How dedicated nodes stand out among other private nodes, and why are they important? Here, we’ll explore this question, using Solana as an example. So, again, get ready—and let’s go!
Introduction to Solana private and dedicated nodes
Why explore this question at all? Why do I need to know when to run a private node for Solana, or set up a dedicated node?
Basically, the difference is in who manages your node—you, or an external party. The conditions and price will differ significantly depending on it.
Look at the diagram below showing the difference between shared, dedicated, and VPS (virtual private server) hosting types. In the same way, it shows the differences between the node categories we’ll review here.
Source: DreamHost
A blockchain node is a highly specialized type of server, so they are very similar in terms of infrastructure. They both use computational resources to solve user problems. Usually, web servers are used to store data or perform computations—and blockchain nodes perform these functions, too.
They store blockchain data, synchronize it with other nodes, and communicate with decentralized applications (dApps) using remote procedure calls (RPC) interface. All dApps use RPC nodes to realize blockchain functionalities, so every Web3 developer needs them. Below, one can see how an RPC node works.
Source: CoinGecko
If you want a private node, then you’ll be responsible for maintaining it and ensuring it proceeds all requests as intended. Let’s look closer.
What is a private Solana node?
Imagine a closed server, which only you can access. It’s protected by a cryptographic password and is hosted either via the cloud provider or on your own hardware. You and only you are responsible for anything happening there, such as configuring the server’s features and making sure that it won’t shut down during work.
Essentially, that server is your private node. It can be characterized by:
- exclusive access
- self-management
You get cloud storage on a sufficiently powerful server to run a full Solana node, but in all other aspects, you work with a node by yourself. Configuration, maintenance, request handling—all of that are on your side, with little or no support from the provider. While it may be cheaper and give you more control, it also means more time and responsibility.
A private node can be hosted on your own machine, too—in that case, it will be the same as a dedicated node, and no differences can be applied at all. However, it means that you’re also responsible for setting up all required hardware and software. For Solana full nodes, hardware requirements are very high, so using a node provider is always a good idea!
More about that is below, and now let’s compare it with Solana's dedicated RPC node.
What is a dedicated Solana node?
So, while these two types look pretty similar, they have different purposes.
A dedicated node is managed by an external party (such as our glorious tech team) and you receive exclusive access to it by ordering the API endpoint. An external party is responsible for the node maintenance and provides you with all required support, including setting up the node according to your project’s needs. Therefore, you save a lot of time, money, and effort.
Just relax and focus on your project—all infrastructure is already working!
Key differences between private and dedicated node
Dedicated nodes stand out among other private nodes, providing much higher performance and requiring much less user resources for maintenance. That’s why they’re indispensable for any serious blockchain project.
Look at the details in the table below.
| Characteristics | Private Solana node | Dedicated Solana node |
|---|---|---|
| Access | API-based, several users may access one node | API-based, a node is always exclusive for one user |
| Support | General support and maintenance | Dedicated support and maintenance |
| Performance | Speed and resource limits are present | Unlimited speed and resources with node optimization |
So, with a dedicated node, you’re already supplied with the infrastructure required for your project and don’t need to set it up yourself. A self-managed private node enables more control and is usually cheaper, but a dedicated node is superior both in performance and reliability.
Solana private RPC node: How it works
As one can see, both private and dedicated nodes share one quality: they are exclusive. Only those with permission can access and use a node, whether one or several people. On the other hand, there are public RPC nodes with shared access. They are much more affordable and provide flexibility, but their performance is lower, as expected.
Private RPC vs public RPC
As one can recall from the first diagram, public nodes are accessed by multiple users, who share their computational resources. Let’s compare them with private nodes.
Public RPC nodes can usually be accessed by many people, and the limitation is the number of computational resources they can use. All users with a public RPC endpoint connect to the same nodes and use resources allocated to each of them.
Private RPC nodes have much more personalized access. When one person has a private RPC endpoint, no other person can have the endpoint of this node, so all its computational resources are dedicated to that user.
Thus, a private RPC node will always have superior performance. Don’t confuse our paid shared nodes with public ones! They are private, too: no one can access them except our subscribers. When you pay for a shared node, you pay for the compute units (CUs) that you can use to call blockchain methods.
Once a project gains traction and becomes popular, it’ll most likely need a dedicated node.
Benefits of a private RPC node
Let’s summarize the public and private RPC differences, so one can clearly see the advantages of a private RPC node.
| Private Solana RPC | Public Solana RPC |
|---|---|
| Exclusive access | Shared access |
| Stable performance | Performance may vary |
| High personalization | Little personalization |
| Dedicated support | General support only |
| Higher costs | Reduced costs |
A private node ensures stable performance, can be personalized according to your needs, and often includes full personalized support. That’s why it’s always preferable for middle- and large-size blockchain projects, while public nodes may be OK to test small projects.
Why choose a Solana dedicated node?
Here is the short answer: for building and deploying large-scale projects. Let’s now dive into details.
Reliable infrastructure and performance
A dedicated node is the most secure and reliable blockchain infrastructure that one can even access. Usually, it even outperforms the self-hosting services, as a node provider has dedicated tech and support teams who monitor nodes’ performance 24/7 and help with any issue. So, developers get stability and support, while being able to focus on their projects.
Managed vs self-hosted dedicated nodes
Another big benefit of dedicated nodes is personalization. It includes personalized support and high node optimization specifically for a user’s project. Node provider teams can set up the node as required to ensure the best performance, and a user will take the result very quickly.
Conversely, if a user chooses to host a node themselves, it means tens of hours required to set up hardware, install software, and maintain the node’s functionality. Every project requires different configurations, while occasional shutdowns are possible and must be managed. Using a dedicated node service eliminates this issue.
Best use cases for dedicated nodes
Dedicated nodes are needed for projects that proceed with thousands of blockchain requests per hour, or even per minute. Every large blockchain project can fall into this category, especially if many people use it simultaneously or if it has to provide on-chain data very quickly.
Let’s look at two prominent examples from GetBlock’s experience.
DropsTab is a platform that tracks cryptocurrency prices in real time and allows users to set up custom alerts. They are highly useful, for example, in trading. GetBlock provides a fast and stable node for the service, so its users can get notifications just in time, at the same moment when an on-chain event occurs.
Gem Wallet is a general-purpose crypto wallet for multiple chains, with a simple interface and crypto app connections. It’s one of the best choices for casual crypto users who want to keep their assets safe and access them when needed. To handle all of them, Gem Wallet needs a reliable infrastructure—and GetBlock provides it.
You can read more about other GetBlock’s use cases here.
Source: GetBlock use cases
Crypto wallets, decentralized exchanges, trading bots, and security services are some examples of projects that will need a dedicated node once they gain enough traction. While small projects would better start with shared nodes, they will eventually outgrow them.
That’s the answer to why choose the dedicated Solana RPC node.
Setting up a private or dedicated Solana node
So, as we see, both private and dedicated nodes are exclusive. They only differ in terms of organization and resource allocation.
Therefore, now we can explore how one can set up the node and what one needs for that—and why using a node provider is still an excellent idea.
Hardware and network requirements
Requirements for a private RPC node on Solana are quite high. As you probably know, Solana is often labeled as the fastest and the most efficient blockchain for now. While this is somewhat close to the truth, such a performance requires significant resources.
First, you need the following set of hardware:
- More than 256 GB RAM
- More than 1 TB of disk space
- More than 1 Gbit/s Internet connection
- At least 24-core CPU, AMD preferred
Solana produces new blocks very quickly and checks its condition with a very high frequency, that’s why its RAM and Internet speed requirements are significantly larger than those for most other chains, such as Ethereum.
You can read more in our full-scale Solana node guide.
Deployment options (self-hosted vs provider solutions)
After the hardware is ready, you need to install the required software. It can be found in our guide, and you can also check Solana’s official documentation.
In includes:
- A Linux OS, usually Ubuntu of the latest version
- Solana’s command line interface (CLI) client
- Hardware port configuration for synchronization
Usually, one has to set up the node to synchronize with other nodes and also to proceed with RPC requests, needed to implement Solana methods. It requires learning Solana documentation and getting experience in node maintenance. Various complications may emerge during the process, depending on how many requests should be processed and which methods will be implemented. All these peculiarities should be counted when running an RPC node.
That’s why using a node provider saves a lot of time. While you give up some level of control, you get support and stability.
If you have a project idea and are ready to build your MVP, you can calculate by yourself which option will be less expensive and more viable for you. Don’t forget: our plans are very flexible, and even the cheapest annual plan for $39/month will be more than enough for the initial project launch. Moreover, you may host it on our Dapp Hub after the launch and get our help for your further development!
Conclusion
The reason why we have different terms for private and dedicated nodes is that they express different resource allocation methods.
When you host a node, it’s always your node—but it’s often too expensive and takes too much time and effort. So, you can either order a dedicated node, optimized for your activities or set up a self-managed private node in a cloud. The first option provides higher performance, is more convenient, and costs more. The second one requires personal node administration, which takes time and responsibility—and lets you do everything as you want.
When performance is the key indicator, a dedicated node is what you need. When a specifically configured node is required, and you’re ready to take responsibility for it—choose a private node. That’s the summary.
When to choose a dedicated Solana node?
Here are two questions to consider:
- Which specific node configurations are needed for my application?
- How many blockchain requests are generated via my apps each hour?
If your app requires specific configurations and/or needs many thousands of requests to be processed every hour, then a dedicated node is absolutely the best choice for you. After all, that’s all the questions of budget and stability, so be sure to calculate how much revenue your project is going to generate and whether a dedicated node boosts it or saves your expenses.
If yes, without further ado—sign up to GetBlock and select your plan!
