idea around a personal event server
Go to file
Vincent Batts 2495d59df0
README: link to an event specification
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-01-08 16:15:34 -05:00
.gitignore Initial commit 2018-12-17 13:58:30 -05:00
LICENSE Initial commit 2018-12-17 13:58:30 -05:00
README.md README: link to an event specification 2019-01-08 16:15:34 -05:00

README.md

idea-personal-event-srv

idea around a personal event server

overview

Ideally it would be a network of agents, that can broadcast and see messages, only responding to interested events. A brokerless setup. 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