Stellar is an open-source network that connects multiple nodes. They are computers that maintain a shared distributed ledger. To validate and add transactions, the nodes communicate with one other. Stellar Core is an implementation the Stellar Consensus Protocol. It is used by nodes to keep in sync while they work on validating transactions, and then applying them to a ledger.

Types and types of nodes

Stellar nodes have the same basic functions: Stellar Core runs, connects to peers, handles transactions, stores the ledger’s status in SQL database, and keeps a copy of it in flat XDR file called buckets. Horizon is the Stellar API that all nodes support. Two key configuration options are what determine the behavior of a node. A node can:

• Participate in consensus for transitions validity

• Publishing an archive allows other nodes to access it and view its complete history.

Environment setup

Stellar core can be installed in many ways. You can configure it to join the network at different levels. Watcher, Basic Validator, or Full Validator. It does not matter how Stellar Core has been installed. All that is required is to connect to peer-to-peer networks, store the ledger’s status in the database, connect to the Stellar API and Horizon.

Calculate your requirements

Stellar Core PostgreSQL is well-suited for an m5.large AWS server with dual-core Intel Xenon processors and 8GB RAM. Storage wise, 1 TB is suggested as sufficient.

Network access

Stellar Core connects via peer-to-peer networks to keep the ledger synchronized. This means that each node must have specific TCP ports open for outbound and inbound communication.

Inbound:

Stellar Core’s node allows IPs to connect over TCP to its PEER_PORT. Stellar Core allows you to specify a port while configuring it, but the default (11625), will be used.

Outbound:

Stellar Core will need to connect with other nodes via PEER_PORT and TCP. Stellarbeat has information on other PEER_PORT nodes.

Read More : https://www.leewayhertz.com/run-stellar-core-node/