How to Save Time on DevOps and Scale With Infura: Lessons from Leading Ethereum Dapps

The pros and cons of running your own Ethereum node and different ways leading dapp teams are using Infura to scale their infrastructure.

The Pros and Cons of Running Your Own Node

One of the most powerful propositions of the Ethereum blockchain is that theoretically, anyone can run a node, validate transactions, and contribute to the network. If you’re a veteran Ethereum developer, spinning up and running a node might have been one of the first things you did when you entered this space.

However, syncing an Ethereum node and storing the blockchain data can be time-consuming (days), costly (500 GB of storage, or more), and finicky (if you shut down your client improperly, if your disk isn’t an SSD, if your Internet drops out, etc). If you’re hoping to build a popular dapp, you’ll eventually need to scale your infrastructure to accommodate new users and higher transaction volume. This means more nodes, more disk space, full-time infrastructure engineers, and ultimately more costs. If you need to pin data to IPFS, access full node archive data, or upgrade your nodes to stay compatible with network hard forks, maintaining infrastructure only gets more complex.

In this how-to, we walk through different ways to scale your infrastructure and showcase how leading dapp teams are using Infura’s APIs to meet demand during these unprecedented times of network activity.

Read the full story on the ConsenSys blog

Originally published at

How to Save Time on DevOps and Scale With Infura: Lessons from Leading Ethereum Dapps was originally published in ConsenSys Media on Medium, where people are continuing the conversation by highlighting and responding to this story.

—Source link—

What do you think?

The Physical World Will Be More Nationalistic, The Digital World Will Be More Global

Our Network: Issue #19