Fixes #158 - Add a directory for Architectural Decision Records

skupperproject · Mar 10, 2022 · fbc378a · fbc378a
1 parent 812ffde
commit fbc378a
Show file tree

Hide file tree

Showing 3 changed files with 43 additions and 0 deletions.
diff --git a/.adr-dir b/.adr-dir
@@ -0,0 +1 @@
+decisions
diff --git a/decisions/0001-record-architecture-decisions.md b/decisions/0001-record-architecture-decisions.md
@@ -0,0 +1,19 @@
+# 1. Record architecture decisions
+
+Date: 2022-02-09
+
+## Status
+
+Accepted
+
+## Context
+
+We need to record the architectural decisions made on this project.
+
+## Decision
+
+We will use Architecture Decision Records, as [described by Michael Nygard](http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions).
+
+## Consequences
+
+See Michael Nygard's article, linked above. For a lightweight ADR toolset, see Nat Pryce's [adr-tools](https://github.com/npryce/adr-tools).
diff --git a/decisions/0002-remove-link-routing-from-the-router.md b/decisions/0002-remove-link-routing-from-the-router.md
@@ -0,0 +1,23 @@
+# 2. Remove Link-Routing from the router
+
+Date: 2022-02-11
+
+## Status
+
+Accepted
+
+## Context
+
+In the interest of removing complexity from the router and in removing an entire dimension of testing, it has been decided that link-routing shall be removed from the router code base.
+
+## Decision
+
+Link routing, including the transaction coordinator, shall be removed from the router.
+
+## Consequences
+
+The _interesting_ capabilities of link routing can be replicated using streamed messages and intermediate delivery dispositions.
+
+Link routing is not needed for Skupper.
+
+This also has the effect of removing the asynchronous address lookup in edge routers that was needed to determine if an address was a link-routed address.  This will greatly improve the latency experienced in local traffic in an edge cloud.