Replies: 3 comments 1 reply
-
I'm reading to catch up on these topics: https://www.weave.works/technologies/going-cloud-native-6-essential-things-you-need-to-know/ This resonates with me a lot. |
Beta Was this translation helpful? Give feedback.
1 reply
-
Post-launch idea: Publishing our cluster health checks live on the website. Particularly useful if the GitHub and Twitter oracle network is white-labelled for other projects to use as well. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
One of the major reasons I became interested in ChainLink over every other blockchain endeavor is because of its focus on smart contracts over tokens, and the way in which operating nodes and writing external adapters allowed me to leverage my traditional software development skills in this new space.
In particular, since availability is a major point of reputation and trust for node operators, we'll want our infra to be rock solid, aka "11 nines" available (99.999999999%).
Let's use this discussion to organize ideas on how to make that possible with solid DevOps, Infrastructure as Code, orchestration and cloud native practices.
Linkpool is doing well in this I've noticed, publishing Terraform scripts for operating ChainLink nodes in the cloud: https://registry.terraform.io/providers/linkpoolio/chainlink/latest/docs
Beta Was this translation helpful? Give feedback.
All reactions