This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
connectivity-suite:architecture [2019/11/01 13:53] voegeli |
connectivity-suite:architecture [2019/11/06 13:00] voegeli [Introduction] |
||
---|---|---|---|
Line 11: | Line 11: | ||
*User interface: Web interface accessible by https (SSL + OpenID). | *User interface: Web interface accessible by https (SSL + OpenID). | ||
- | *Middleware: Establishes the communication between the User Interface and the microservices in the Core for a scalable, robust and distributed system. The Middleware runs in a separated container | + | *Middleware: Establishes the communication between the User Interface and the microservices in the Core for a scalable, robust and distributed system. The Middleware runs in a separate container |
- | *Core: in the core several microservices (Keycloak, Inventory, Configuration, Deployment, Health, Identity Server) are running which are servicing REST API requests. | + | *Core: In the core several microservices (Keycloak, Inventory, Configuration, Deployment, Health, Identity Server) are running which are servicing REST API requests. |
The solution can be used in standalone mode by using the interactive user interface provided by NetModule or by integrating the Connectivity Suite into customer applications by using the powerful REST API. | The solution can be used in standalone mode by using the interactive user interface provided by NetModule or by integrating the Connectivity Suite into customer applications by using the powerful REST API. |