Commit c38a52cd authored by Michel Roy's avatar Michel Roy
Browse files

Update WIP-preliminary-architecture/README.md

parent 5d3db6a3

WIP-preliminary-architecture/README.md

+8 −8
Original line number Diff line number Diff line
@@ -21,24 +21,24 @@ MEC Sandbox... 


MEC Sandbox Backend is composed of two main components:

- _Core Platform_ (single instance - always present)

  - this is the main portal of MEC Sandbox & provides the user sandboxes control plane

  - this is the main portal of MEC Sandbox & provides the user sandboxes control plane & user plane

- _User Sandbox Instances_ (0+ instances)

  - these are the user's private area for experimenting with MEC Services



MEC Sandbox Frontend:

- MEC Sandbox Web-Application

- MEC Sandbox Web-Application (Single Page Application)

  - this is the main user interface to the MEC Sandbox

  - it allows a user to control/configure its own sandbox

  - it allows a user to observe/experiment with MEC APIs present in the user sandbox

  - See [Sandbox-User-Interface](../sandbox-user-interface/README.md) for details on the Web-Application

  - See [Sandbox-User-Interface](https://forge.etsi.org/rep/stf-587/mec-sandbox-scenarios/blob/master/Sandbox-User-Interface/README.md) for details on the Web-Application

- User's Edge Application

  - this is for developers that want to integrate their edge application with a MEC API to experiment & learn





#### Core Platform

A common web-application used by a set of users to instantiate User-Sandbox(es)

A common web-service used by a set of users to control the lifecycle of their respective user-sandbox(es)

- Portal Backend are micro-services (Dockers containers)

- Portal Frontend is a Single Page Application (SPA)

- Serving Frontend files

- Cardinality

  - Typically a single global portal

  - Multiple independent instances possible (ex. development vs production portal)
@@ -58,10 +58,10 @@ A common web-application used by a set of users to instantiate User-Sandbox(es) 
#### User Sandbox

A scenario area reserved for a specific user to experiment with MEC Services

- Cardinality

  - Typically a single user-sandbox per user

  - Typically a single user-sandbox per signed in user

  - Multiple user-sandboxes may be allowed for super-users/developers/etc.

Backend

Composed of MEC services and some scenario control micro-services

- Backend

  - Composed of MEC services and some scenario control micro-services



## Dynamic View