dcae doc cleanup

Remove old markdown platform doc

Change-Id: I592775a24d17d7d786708cde008703f4d899946c
Signed-off-by: VENKATESH KUMAR <vv770d@att.com>
Issue-ID: DCAEGEN2-1891
Signed-off-by: VENKATESH KUMAR <vv770d@att.com>

1 files changed, 0 insertions, 15 deletions

diff --git a/platformdoc/docs/architecture/service-discovery.md b/platformdoc/docs/architecture/service-discovery.md
deleted file mode 100644
index 9831efcf..00000000
--- a/platformdoc/docs/architecture/service-discovery.md
+++ /dev/null
@@ -1,15 +0,0 @@
-# Service Discovery
-
-Service discovery is an architecture pattern used for components (micro-services) to locate each other.  The DCAE platform uses [server-side discovery](http://microservices.io/patterns/server-side-discovery.html) and is using [Consul](https://www.consul.io/) as the service registry solution.
-
-## Service Registration
-
-All components are required to register with Consul in order to be discovered.  There are two methods of registration: self and 3rd party.  The DCAE platform uses 3rd party registration which means components don't actually make the registration calls but defers that responsibility to a platform service.
-
-### Implementation for Docker
-
-[Registrator](http://gliderlabs.com/registrator/latest/) is an open source application that is responsible for registering all components that run as Docker containers.  Registrator watches the local Docker engine's activity log and will register and unregister a Docker container when the container is started and stopped.
-
-### Implementation for CDAP
-
-The CDAP broker is a REST web service that is responsible for registering all components that run as CDAP applications.