From 9272f3232fe3c805226d80826b94f6ac79f5c595 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Daniel=20P=C3=B6tzinger?= Date: Tue, 4 Apr 2017 11:48:39 +0200 Subject: [PATCH] Add tool link --- radar/2017-03-01/microservices.md | 1 + 1 file changed, 1 insertion(+) diff --git a/radar/2017-03-01/microservices.md b/radar/2017-03-01/microservices.md index 6c6b575..4bc674f 100644 --- a/radar/2017-03-01/microservices.md +++ b/radar/2017-03-01/microservices.md @@ -18,5 +18,6 @@ The benefits we see are: * flexibility in deploying changes to production - by just deploying the changed service Related patterns are [Strategic Domain Driven Design](/methods-and-patterns/strategic-domain-driven-design.html) as an approach to wisely cut your architecture according to useful bounded contexts and decide on the relevant communication and "translation" between the services. +In case you are looking for a small visualisation tool for your microservice architecture you might find [vistecture](https://github.com/AOEpeople/vistecture/) useful. Also [Resilience thinking](/methods-and-patterns/resilience-thinking.html) is especially important when designing an application as a suite of microservices.