Skip to content

Commit

Permalink
risks
Browse files Browse the repository at this point in the history
  • Loading branch information
Marc Gorzala committed Nov 25, 2023
1 parent f45fe35 commit dcc8ec8
Show file tree
Hide file tree
Showing 4 changed files with 15 additions and 11 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -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
|===
Original file line number Diff line number Diff line change
Expand Up @@ -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 <<score>>.


=== Process of how we are sending emails

TBD
Now the recommendation service can return for each dancer, a list of all dancers within a distance of 200km together with the computed <<score>>.
Original file line number Diff line number Diff line change
@@ -1,3 +1,4 @@
[[section-concepts]]
== Cross-cutting Concepts

TBD
Original file line number Diff line number Diff line change
@@ -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.

0 comments on commit dcc8ec8

Please sign in to comment.