Scaling INFURA: Not All API Calls are Equal

Michael Wuehler
ConsenSys Media
Published in
2 min readAug 24, 2017

The INFURA team continues to grow and scale along with Ethereum itself. As a core infrastructure provider to the public Ethereum networks, the demands on our infrastructure over the last several months have been sizable. Fueled in large part by ERC20 token sale activity and ENS registrations, the main Ethereum network is handling about 400,000 transactions per day. These transactions all arrive into the Ethereum network through a node that relays it eventually to a miner who packages it in a block. INFURA is one such gateway that these transactions relay through as they find their way into the chain.

Beyond these 400,000 “write” transactions per day, the Ethereum network supporting decentralized applications handles many more “read” requests in the form of JSON RPC API calls. Just as with traditional web development, the number of read requests are often orders of magnitude larger than the write requests. INFURA is routinely servicing over 600 million of these “read” requests per day. We continue to work on back-end infrastructure to ensure these requests are served lightning-fast and reliably.

Continue reading on the INFURA blog

Like this piece? Sign up here for our weekly newsletter.

Disclaimer: The views expressed by the author above do not necessarily represent the views of Consensys AG. ConsenSys is a decentralized community with ConsenSys Media being a platform for members to freely express their diverse ideas and perspectives. To learn more about ConsenSys and Ethereum, please visit our website.

--

--