Common deployments (Web & Desktop)

The following diagrams show common deployments and usage scenarios for KaDeck Web and KaDeck Desktop in companies.

The icons used show an architecture on AWS. However, the same scenarios can be implemented with the corresponding counterparts of the respective cloud environments (Google Cloud, Azure, ...). Also, the scenarios are transferable to on-prem infrastructures in simple steps. If you have any questions, please contact our solution architects.

 

Separate environments

The network environments of all environments (DEV, UAT, and Prod) are separated from each other. Thus, a service from one environment cannot communicate with a service from another environment.

mceclip0.png

In this case, one KaDeck Web package license is required per environment. Alternatively, if the Apache Kafka cluster can be accessed via the employees' computers, KaDeck Desktop can also be used (as for the DEV environment).

For security reasons, a production environment should always be inaccessible from the outside.

 

Combined environments with a separated production environment

The DEV and UAT network environments are not separated from each other. A service from one environment can therefore communicate with a service from another environment. Alternatively, it is possible to define services that are located outside the two environments and can access both environments.

mceclip1.png

In this case, only one KaDeck Web package license is required for DEV & UAT. KaDeck Web can (just like KaDeck Desktop) manage multiple connections and configurations in parallel.

For security reasons, a production environment should always be inaccessible from the outside.

In the example scenario, two KaDeck Web package licenses are required

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.