readme
This commit is contained in:
20
README.md
20
README.md
@@ -114,7 +114,7 @@ As a cloud-native approach, we will take blob storage as a service-independent m
|
|||||||
|
|
||||||
### System Architecture
|
### System Architecture
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
At system level, since identity and data providers are not controlled parts, there are three main components:
|
At system level, since identity and data providers are not controlled parts, there are three main components:
|
||||||
|
|
||||||
@@ -122,7 +122,7 @@ At system level, since identity and data providers are not controlled parts, the
|
|||||||
- BFF
|
- BFF
|
||||||
- Backend
|
- Backend
|
||||||
|
|
||||||
Frontend will speak ONLY with BFF via REST comands. Only sensible data will be encrypted via AES.
|
Frontend will speak ONLY with BFF via REST commands. Only sensible data will be encrypted via AES.
|
||||||
Frontend will GET lazily all the images for galleries.
|
Frontend will GET lazily all the images for galleries.
|
||||||
|
|
||||||
BFF will redirect GET image requests to configured CDN or will serve them if no CDN is configured.
|
BFF will redirect GET image requests to configured CDN or will serve them if no CDN is configured.
|
||||||
@@ -133,7 +133,7 @@ Backend will contact Identity Providers such as Google or Instagram at login tim
|
|||||||
Backend will generate and validate login tokens.
|
Backend will generate and validate login tokens.
|
||||||
Backend will create, retrieve, edit and delete user and image data.
|
Backend will create, retrieve, edit and delete user and image data.
|
||||||
|
|
||||||
Since frontend will be device dependant at a future, BFF will give flexibility for identifying client users.
|
Since frontend will be device dependent in the future, BFF will give flexibility for identifying client users.
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
@@ -178,3 +178,17 @@ __DAPR (Distributed Application Runtime):__ A runtime that simplifies building d
|
|||||||
__Edge Computing:__ A distributed computing paradigm that brings computation and data storage closer to the location where it is needed to improve response times and save bandwidth.
|
__Edge Computing:__ A distributed computing paradigm that brings computation and data storage closer to the location where it is needed to improve response times and save bandwidth.
|
||||||
|
|
||||||
__Parallel Processing:__ A method of processing data in which multiple processors execute tasks simultaneously to increase efficiency and performance.
|
__Parallel Processing:__ A method of processing data in which multiple processors execute tasks simultaneously to increase efficiency and performance.
|
||||||
|
|
||||||
|
__API (Application Programming Interface):__ Un conjunto de definiciones y protocolos para construir e integrar software de aplicaciones.
|
||||||
|
|
||||||
|
__OAuth:__ Un estándar abierto para la autorización que permite a los usuarios compartir recursos entre aplicaciones sin compartir credenciales.
|
||||||
|
|
||||||
|
__CI/CD (Continuous Integration/Continuous Deployment):__ Un conjunto de prácticas que automatizan el desarrollo, las pruebas y la implementación de software.
|
||||||
|
|
||||||
|
__Microservicios:__ Un estilo arquitectónico que estructura una aplicación como un conjunto de servicios pequeños y autónomos.
|
||||||
|
|
||||||
|
__Load Balancer:__ Un dispositivo o software que distribuye tráfico de red o aplicación entre varios servidores para mejorar la eficiencia y la disponibilidad.
|
||||||
|
|
||||||
|
__Cache:__ Un almacenamiento temporal de datos para acelerar el acceso a información frecuentemente utilizada.
|
||||||
|
|
||||||
|
__JWT (JSON Web Token):__ Un estándar para transmitir información de forma segura entre partes como un objeto JSON.
|
||||||
|
Before Width: | Height: | Size: 45 KiB After Width: | Height: | Size: 45 KiB |
Reference in New Issue
Block a user