search

magneticio / vamp.io

the vamp.io website
Apache License 2.0
24 stars 17 forks source link

create content for /how vamp works/topologies #48

Open gggina opened 7 years ago

gggina commented 7 years ago

(f.e. with or without containers, vamp in or outside docker cluster, elastic search or something else, AWS with ELB

gggina commented 7 years ago

create content and diagram for "Vamp router only" setup: there seems to be interest in a Vamp setup that "only" uses the programmable routing part of Vamp (i.e. the VGA+Haproxy's), because it's less intrusive when not using containers and/or micro services yet, but still wants to do programmable routing for canary-routing etc.

I've sketched out a quick diagram for a Vamp+bitsensor setup which does realtime application intrusion detection and mitigation (https://bitsensor.io/blog/achieving-devsecops-by-instrumenting-microservices-orchestration-in-vamp) but we can remove the bitsensor parts here and only show Vamp components in the diagram, describe how to install and set this up in a typical 3-tier application landscape, and what features are available then.

(NB we might need to create a special package/config for this to disable container-related features of Vamp in the UI/API though. Including @iamtew and @dragoslav because of this)

image