+ sysdesign v0.5

- new abstract

chapters/architecture/System-Design.typ

@@ -1,5 +1,24 @@
 == System Design
 
+=== Clients
+
+The rvault server is compliant with any client acting in compliance with the hashicorp vault api specification.
+To achieve this, tests are written using the official Hashicorp vault go client. 
+
+=== Webserver
+
+The Webserver forwards client requests to different routers according to the request paths:
+i.e. "/v1/auth" for the authorization router.
+Those routers map request to their corresponding handlers.
+
+Problem: 
+- TODO describe middleware
+
+=== Engines
+
+
+
+=== Storage
 
 Engines:
 
@@ -20,9 +39,9 @@ Momentan beschränken wir uns auf SQLite
   ],
 )
 
+=== Design decisions
 
 
-=== Problem Description
 
 // + The API to implement e.g. has the concept of mount points (similar to how filesystems can be mounted on UNIX-like systems).
 // 	Mount points can contain multiple slashes.

documentation.typ

@@ -9,7 +9,7 @@
   ),
   // Insert your abstract after the colon, wrapped in brackets.
   // Example: `abstract: [This is my abstract...]`
-   abstract: [The goal of this project is to implement the HashiCorp Vault in Rust. During this project we have developed an architecture and started implementatino of some basic cases for key-value-storage. Further development is needed to pursue the goal of reaching compatability with the original version written in Go.],
+   abstract: [The goal of this project is to implement the HashiCorp Vault in Rust. During this project we have developed an architecture and started implementation of some cases for key-value-storage. Further development is needed to achieve feature parity with the original version written in Go.],
   // keywords: ("First keyword", "Second keyword", "etc."),
   date: "2024-06-02",
 )