added some more text for data storage and auth
This commit is contained in:
parent
7a744daff1
commit
4435ff7654
10
readme.md
10
readme.md
|
@ -139,11 +139,17 @@ Vertical scaling also allow for redundancy and 99.99% uptime as services can be
|
||||||
|
|
||||||
## Authentication
|
## Authentication
|
||||||
|
|
||||||
For authentication Keycloak will be used to minimize security holes.
|
Considering the nature of our project it is extremely important to make authentication as secure as possible, although it's debatable if it's as importand as at a Banking service for example. Still, security around auth is one of the most basic services.
|
||||||
|
|
||||||
|
And as such, for authentication Keycloak will be used to minimize security holes, as it's open-source, extensible, performant, and customizable.
|
||||||
|
|
||||||
## Data storage
|
## Data storage
|
||||||
|
|
||||||
For storing data PostgreSQL will be used as it is one of the most performant databses out there. For object storage S3 [garage](https://garagehq.deuxfleurs.fr/) will be used as it is geo-located and really easy to deploy.
|
Our objective with data storage was to provide a safe, reliable, and well performing method of storing data, which is not only a must have, but is also one of the elementary requirements for any project - let it be small or big - with more complex data handling. Knowing this, PostgreSQL caught our eye, whlist not only meeting our demands for standards, but also having a strong reputation for itself.
|
||||||
|
|
||||||
|
We truly think that with this ORDBMS (object-relational database management system), we chose adaquate considering the competition of DBM systems.
|
||||||
|
|
||||||
|
For object storage S3 [garage](https://garagehq.deuxfleurs.fr/) will be used considering it's geo-located property and ease of use.
|
||||||
|
|
||||||
## Load balancing
|
## Load balancing
|
||||||
|
|
||||||
|
|
Reference in a new issue