learner-long-life/gist:edbacf61517bb9100b742b69ccd5fbc1

## gistfile1.txt
As for running your own Ethereum node, that's what you might want to do if you are going to be
making many smart contract calls for your users. Most people use Infura's free public nodes for
casual calls or development, but when they have a production system, they have to pay per 1000
smart contract calls or they can run their own dedicated Ethereum nodes. This involves maintaining
a Linux system and syncing the blockchain, and people who do this often use Amazon's hosted service, AWS.
I suspect Infura also uses AWS.

So for the same AWS credits, you could run a subgraph / GraphQL server to index the Ethereum events,
and have your front-end query it much more efficiently each time a user refreshes your website, instead
of calling the Ethereum mapping getter method repeatedly. You'll probably want to run your own subgraph server,
but this is much easier than running your own Ethereum node.
	As for running your own Ethereum node, that's what you might want to do if you are going to be
	making many smart contract calls for your users. Most people use Infura's free public nodes for
	casual calls or development, but when they have a production system, they have to pay per 1000
	smart contract calls or they can run their own dedicated Ethereum nodes. This involves maintaining
	a Linux system and syncing the blockchain, and people who do this often use Amazon's hosted service, AWS.
	I suspect Infura also uses AWS.

	So for the same AWS credits, you could run a subgraph / GraphQL server to index the Ethereum events,
	and have your front-end query it much more efficiently each time a user refreshes your website, instead
	of calling the Ethereum mapping getter method repeatedly. You'll probably want to run your own subgraph server,
	but this is much easier than running your own Ethereum node.