From 7847ad62f164d4796201f0b4d5ea384a37c5f6ec Mon Sep 17 00:00:00 2001 From: Vincent Batts Date: Thu, 20 Dec 2018 17:28:12 -0500 Subject: [PATCH] more thoughts --- README.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/README.md b/README.md index 327a910..abb4407 100644 --- a/README.md +++ b/README.md @@ -10,6 +10,19 @@ Further, having one or more endpoints for recieving, and even calling webhooks. The webhooks must be a specified node. Perhaps the webhooks recieved would broadcast a message on the node network, and specific types of node network messages would translate out to calling a webhook. +## Use-cases + +* agent on a node doing a liveness check on a service +* agent on a node sending metric like battery power status change +* container build event +* curl for modtime change, and sync a repo + +## Alternate approach + +Since there is data pushed and data pulled, as well as new services brought in and services expected, consul.io is a very possible project to use. +Publishing services is interesting, but maybe not the connect proxy for routing. +Primarily for kv usage, and possibly for liveness testing of services in the datacenter. + # references * https://github.com/adnanh/webhook