From c3e58998dfbe156b31da87792b6e5ee6e1bc9792 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Daniel=20P=C3=B6tzinger?= Date: Sat, 19 Oct 2019 21:35:30 +0200 Subject: [PATCH] add crosslink --- radar/2019-11-01/flamingo.md | 2 +- radar/2019-11-01/ports-and-adapters.md | 6 ++++++ 2 files changed, 7 insertions(+), 1 deletion(-) create mode 100644 radar/2019-11-01/ports-and-adapters.md diff --git a/radar/2019-11-01/flamingo.md b/radar/2019-11-01/flamingo.md index 42690c4..62f5022 100644 --- a/radar/2019-11-01/flamingo.md +++ b/radar/2019-11-01/flamingo.md @@ -32,7 +32,7 @@ Flamingo has a clean architecture with clear dependencies in mind and offers a t * GraphQL support and therefore support to build nice SPA and PWAs on top of it * Resilience and Caching for external APIs calls. -Flamingo itself does not contain ORM Mapper or libraries - instead it emphasizes "ports and adapters" architecture - so that you have a technology free (domain) model and any possible (and replaceable) persitence behind it. +Flamingo itself does not contain ORM Mapper or libraries - instead it emphasizes ["ports and adapters"](/methods-and-patterns/ports-and-adapters.html) architecture - so that you have a technology free (domain) model and any possible (and replaceable) persitence behind it. That makes Flamingo useful to build microservices and applications - especially to build "frontends" or portals that require interaction with other (micro) services in a distributed architecture. When sticking to the architectural recommendation you can build modular applications with replaceable adapters that gives you independed testability. diff --git a/radar/2019-11-01/ports-and-adapters.md b/radar/2019-11-01/ports-and-adapters.md new file mode 100644 index 0000000..b4b494a --- /dev/null +++ b/radar/2019-11-01/ports-and-adapters.md @@ -0,0 +1,6 @@ +--- +title: "Ports and Adapters" +ring: adopt +quadrant: methods-and-patterns + +--- \ No newline at end of file