-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Marc Gorzala
committed
Nov 25, 2023
1 parent
f45fe35
commit dcc8ec8
Showing
4 changed files
with
15 additions
and
11 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1 change: 1 addition & 0 deletions
1
src/main/jbake/content/documentation/arc42/src/08_concepts.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,4 @@ | ||
[[section-concepts]] | ||
== Cross-cutting Concepts | ||
|
||
TBD |
16 changes: 12 additions & 4 deletions
16
src/main/jbake/content/documentation/arc42/src/11_technical_risks.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |