From dcc8ec856e3c144606d8cfcc771cbf7006d7adda Mon Sep 17 00:00:00 2001 From: Marc Gorzala Date: Sat, 25 Nov 2023 10:49:51 +0100 Subject: [PATCH] risks --- .../arc42/src/03_system_scope_and_context.adoc | 2 +- .../documentation/arc42/src/06_runtime_view.adoc | 7 +------ .../documentation/arc42/src/08_concepts.adoc | 1 + .../arc42/src/11_technical_risks.adoc | 16 ++++++++++++---- 4 files changed, 15 insertions(+), 11 deletions(-) diff --git a/src/main/jbake/content/documentation/arc42/src/03_system_scope_and_context.adoc b/src/main/jbake/content/documentation/arc42/src/03_system_scope_and_context.adoc index 5b52feb..229dd67 100644 --- a/src/main/jbake/content/documentation/arc42/src/03_system_scope_and_context.adoc +++ b/src/main/jbake/content/documentation/arc42/src/03_system_scope_and_context.adoc @@ -29,6 +29,6 @@ image:technical-context.drawio.svg[] [options="header", cols="1,5"] |=== | Neighbor | Description -| SMTP-Servier | Used to send emails to it's stakeholders +| SMTP-Server | Used to send emails to its stakeholders | Web-Client | Each Stakeholder will access Dancier by a distinct Web-Application via a Web-Client |=== \ No newline at end of file diff --git a/src/main/jbake/content/documentation/arc42/src/06_runtime_view.adoc b/src/main/jbake/content/documentation/arc42/src/06_runtime_view.adoc index 74bb61b..784ee76 100644 --- a/src/main/jbake/content/documentation/arc42/src/06_runtime_view.adoc +++ b/src/main/jbake/content/documentation/arc42/src/06_runtime_view.adoc @@ -50,9 +50,4 @@ end @enduml .... -Now the recommendation service can return for each dancer, a list of all dancer within a distance of 200km together with the computed <>. - - -=== Process of how we are sending emails - -TBD \ No newline at end of file +Now the recommendation service can return for each dancer, a list of all dancers within a distance of 200km together with the computed <>. diff --git a/src/main/jbake/content/documentation/arc42/src/08_concepts.adoc b/src/main/jbake/content/documentation/arc42/src/08_concepts.adoc index d15468f..9e53e80 100644 --- a/src/main/jbake/content/documentation/arc42/src/08_concepts.adoc +++ b/src/main/jbake/content/documentation/arc42/src/08_concepts.adoc @@ -1,3 +1,4 @@ [[section-concepts]] == Cross-cutting Concepts +TBD \ No newline at end of file diff --git a/src/main/jbake/content/documentation/arc42/src/11_technical_risks.adoc b/src/main/jbake/content/documentation/arc42/src/11_technical_risks.adoc index 7df0ec9..17df48f 100644 --- a/src/main/jbake/content/documentation/arc42/src/11_technical_risks.adoc +++ b/src/main/jbake/content/documentation/arc42/src/11_technical_risks.adoc @@ -1,10 +1,18 @@ [[section-technical-risks]] == Risks and Technical Debts -* Potential Overengineering -* Can we reach the critical mass, that a kind of dating site like this will work -* Adoption of Schools for Dancier is pretty much unclear -* Potential Spam Problem +=== Potential Overengineering +By trying to be an attractive learning project for developers, we are at risk of over-engineering. +One example that falls into this category is that we split the system into more individual microservices as probably needed. A modular monolith would be likely to be easier to maintain and operate. +It is also questionable if Kafka would be a good fit for our messaging requirements. +But we want a project that is a distributed system and uses those technologies that are quite dominant (at least in the companies we have worked). + +We should have a close eye on this, not introduce arbitrary more examples of things like this, to not risk the project as a whole. + + +=== Spam could be a severe problem + +Providing a platform where individuals can chat with each other, could lead to problems with spamming people. As of now, we are not implementing anything against this problem, to get our MVP faster done. This could put us under pressure to react fast in case that turns out to be a problem. \ No newline at end of file