Update Technical future / Andreas

Technical-future-%2F-Andreas.md

@@ -8,6 +8,9 @@
 * No Jakarta Persistence API usage in `core` Maven module.
   * Keep repository interfaces in `core`
   * Move repository implementations to their own module and isolate Jakarta Persistence API to their implementations.
+* Stop with the "1 table-1 entity-1 repository-1 service" thing
+  * A service should work with some context, such as final seminar from a supervisors point-of-view, not the SQL table called "final_seminar"
+  * A repository can manage multiple `@Entity`s (and therefore tables)
 * Remove manual transaction handling inside workers (`AbstractWorker` base class)
 * Make all notifications event-based rather than direct calls from other service methods
 * Make event handling asynchronous (such that a failure or slowdown in an event consumer does not interfere with the event producer)
@@ -31,4 +34,5 @@
 * Make it easier to schedule new jobs
   * Right now you need a bean for the scheduling, a bean for the worker, and finally a bean for the actual job (unless you do it in the worker)
 * Replace Wicket with Spring Web (REST API) + React (TypeScript)
-  * Must have a transition period where both work together simultaneously with smooth transition
+  * Must have a transition period where both work together simultaneously with smooth transition
+* Automatic deployment to production after pull request is merged