A+ A A-

A Day In The Life of a NodeCheck Engineer

What does it take to be a NodeCheck Engineer?  What do we have to do to ensure our site is running in tip-top conditon?

To get a real understanding of what's going on, means knowing how it all sits together.

So you've got the website, which we have to keep running, which means updating the server, ensuring that the web server and database behind it are tuned properly and able to deal with all the requests.  This might not be something that is done on an every day basis, but it would need to be repeated quite regularly to keep on top of things.  Otherwise, we end up with a slow site, bad user experience, and unhappy users.  We need to ensure the site is running fast, so that users can quickly add their masternodes for monitoring, view their masternode info, check the MN/Market stats, and so on.  On top of this we have the API service, so that also increases the load on the servers and have to ensure that it is responsive and fast for our API users.

Then you have the masternode monitoring processes.  We have to run a wallet for every single coin on our platform.  This varies from coin to coin, but each wallet will take a few hundred MB of ram, and some even 1 - 2 GB of ram.  So again, we have to ensure that all the backend servers are running as fast as possible.  Not only that, we have to be pro-active and ensure new wallet releases are updated as soon as possible.  So when they are released, we are compiling them on our test server and preparing our DEB packages to install on our production servers.  Doing this helps to minimise the amount of forks when a missed wallet update has gone through and false notifications being sent because of this.  Why do we make DEB packages?  Well this is simple, we compile it once, and then we can install it on any of our servers.  Imagine a situation, where one of our servers dies, and it was running 20 - 30 wallets?  We'd then have to create a new server, compile 20 - 30 wallets and then get them up and running with the block chain syncing.  Each wallet can take about 10 minutes to compile.  So you can see, in the event of server failure, we could have a few hours or more of downtime.  So, since we have them compiled and ready to install, we can create a server within 5 minutes and install all the coins and everything is ready to run.  We also make bootstraps each week, so that at worst, we only have 7 days to sync the chains.  This would mean maximum 30 - 60 mins before the new server is back online, and service is resumed to 100%!!!

We use devops tools which help us do this, as well as backups and all the usual stuff required to ensure NodeCheck.io is running at the highest standard that you have all come accustomed to using since we started in February 2018.

And last but not least, our outstanding level of support to you all the users, ensuring that your problems are resolved in a quick and efficient matter.  This is why NodeCheck.io is simply the best Masternode Monitoring service by far!