From 1f46d748ac03968a6dc427a966d8041f4602aaa6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cyryl=20P=C5=82otnicki?= Date: Mon, 8 Jul 2024 18:16:33 +0100 Subject: [PATCH] add system architecture template --- fi1/README.md | 2 ++ fi1/system_architecture_template.svg | 1 + 2 files changed, 3 insertions(+) create mode 100644 fi1/system_architecture_template.svg diff --git a/fi1/README.md b/fi1/README.md index 61b749f..b4efcde 100644 --- a/fi1/README.md +++ b/fi1/README.md @@ -138,9 +138,11 @@ Implementation notes: * Idempotency matters, both externally as well as internally. Never assume exactly-once delivery of a message, test extensively with non-zero delivery error rate scenarios. * Avoid synchronous communication with the actors requesting changes - e.g. if using HTTP - don't make clients wait for us to do any processing before we can issue an HTTP response. Store the intent and process later rather than processing in place. +![system architecture template](./system_architecture_template.svg) ## Example processes - modeling and notes To be able to validate the system template and choose specific components from it let's analyse the processes we know of and see how easy it is to implement them. +Would be good to draw sequence diagrams to try to understand different processes. (I ran out of time here, but based on my intuition/experience the template should still work) diff --git a/fi1/system_architecture_template.svg b/fi1/system_architecture_template.svg new file mode 100644 index 0000000..f54afe3 --- /dev/null +++ b/fi1/system_architecture_template.svg @@ -0,0 +1 @@ + \ No newline at end of file