BuildTeam High Performance RPC Full Node Cluster

in #buildteam6 years ago

The https://rpc.buildteam.io is a load balanced cluster of not one but two 512GB NVME Raid Servers and one 256GB SSD server. All servers in the cluster support all plugins and runs as a full node including account history.

Free to use by all

https://rpc.buildteam.io is used by a lot of high profile projects for the STEEM blockchain and is publicly available and free to use.

RPC Performance

Most full nodes were unable to complete this test reliably or even once, without failing.

Below are the response times for all the nodes that completed the test successfully at least once. Some of these were unable to repeat the test without throwing errors.

The simple test consists of returning 100 blocks sequentially.

Node Administration

All node administration and service is performed by witness @themarkymark.


Join our Discord chat

Get support and connect with us and other BuildTeam fans!


We are always looking to improve @buildteam and try to keep you up-to-date whenever something changes. If you have any suggestions about what we should change or add to @buildteam, then please drop by and let us know!


Missed the BuildTeam announcement? Here's all the juicy details.



Visit our flashy new website BuildTeam.io!


Set @buildteam as your witness proxy today and contribute to building a better tomorrow!

Want an easier way? Use our SteemConnect proxy link!


This is a @steemvoter subscription payment post. Thank you to Steemvoter customers for allowing us to use your Steem accounts to upvote this post by virtue of your free subscription to the Steemvoter.com bot service. @steemvoter is proudly a @buildteam subsidiary and sister project to @steemsports and @minnowbooster.

Sort:  

Whoaaaa!

Will definitely use you for my code!

I still don't fully understand what is a rpc-full-node-cluster means. Is it good or bad?

It is very good :) let’s just say that developers build software but need a way for the software to communicate with the blockchain, the rpc nodes allow this to happen, kind of like a “middleman”. Faster nodes mean developers can create software that can handle more users and more transactions, kind of like @steemvoter and @minnowbooster, which process lots of transactions.

Oh and a cluster just means that there are a few nodes working together, so if one fails the others still keep running, also when all three are up means the power of all three are combined to serve even more transaction requests.

Great job guys! RPC nodes are badly needed, and also reliable RPC nodes. Top Notch Job! Thanks

Awesome, thank you. STEEM needs more nodes! I'd like to put one in my location Thailand before long, there's a lot of users here. It's on my very long to do list!

Will you announce downtimes, maintenance, upgrades, etc. for this node?
Would be nice to have a real stable RPC node
cough * api.steemit.com not really * cough

We are currently not doing that publicly but if you run a project that needs this, we may consider it. We already have health checks and monitoring available, but that won't protect us from downtime if steemd has hickups.

no one is protected from steemd hickups;)
but at least maintenance cycles, so ops can switch from one node to another, during that time window.
Like a real service :))

In that case I recommend backup nodes if your library allows them. It can happen that nodes just lock up and just don't respond at all without warning. No one can predict that sadly.

Define stable ...

api.steemit.com is stable enough - otherwise use backup-nodes

define stable enough ;)

Also remember that we provide an rpc node without jussi or appbase or other beta features that made problems in the past. We may change that once we deem them stable enough but for the moment we have users who depend on us not changing node behavior on a whim.

@reggaemuffin

Your RPC-Node is top-notch. Don't get me wrong there. I just believe api.steemit.com is stable enough for most use-cases and in combination with backup-nodes, there shouldn't be any problem there.

Yeah definitely! For small use case they are enough. But once you leave that territory you can be pretty left alone should issues arise (like the current one where api.steemit.com lacks behind on transfer history by days)

they switched to version 0.19.4 without any notice.
This is a no go in any service management.
You have deployment plans, rfcs, etc.
I should write a tutorial for steemit it seems, how to operate a reliable service.

Hi @buildteam! You have received 1.0 SBD tip from @cardboard!

Protip: if you want to send tips and upvotes from @tipU you need to make a deposit first.

Wow this is a great work

Nice evolution, that's good.
i resteem you to french community!!

It's a very good post...!!! thanks to @buildteam

Wow that's a really amazing post dear,very beauty and amazing Well done job by you, i read it and enjoy it, and learn lot of thing's from this post, and i visit your blog many times, and reading your interesting articles and comments on it, So keep it up, and im waiting for your next post, well thanks for sharing with us, Thank You.

@buildteam continues to innovate in the face of cryptocurrency market decline, our vision is long term... the time to build is always now, no matter the circumstances. Markets will rise and fall, but technological advancements will touch the lives of many and leave behind a legacy, this is the heart of @buildteam. Thank you to our builders for the great work in advancing the Steem community. Salute!

Thank you guys! @tipu send 1 sbd tip

We already have health checks and observations available, just like Sharq needs rakha ..

It's a very good post...!!! thanks

Thanks you friend
Nice my post
Good

Excellent tool thanks for your contributions

Is state stored fully in RAM on this node, or should it scale beyond 512GB through using the NVME drives for that too? State must be getting fairly close to that now I'd guess?

Heyy, i am a trader, i come from vietnamese, nice to meet you 🙂

wow so nice post me upvote please upvote me and me new

Loading...