Zum Hauptinhalt springen

Detailed text description: Landscape with a Workspace Router

This page provides a long description of the diagram used in the Workspace Router section of the Landscape Networking article. It shows how the Workspace Router distributes incoming traffic across the services of a Landscape and a custom target.

Overview​

The diagram shows an app user above a landscape deployment area. A custom target sits to the right, outside the landscape.

Main components​

  1. App user:
  • Positioned at the top, outside the landscape.
  • Sends requests to the application.
  1. Workspace Router:
  • Runs as a service at the top of the landscape.
  • Is marked as the Landscape gateway.

  1. Reactive service named frontend.

  2. Reactive service named backend.

  3. Custom target:

  • Positioned outside the landscape.
  • Represents a Kubernetes service or an external URL.

Traffic and routing flow​

  1. The app user sends traffic from either:
  • A custom domain using the pattern customdomain.com/*.
  • The workspace development domain.

  1. All requests first reach the Workspace Router, because it is the Landscape gateway.

  2. The router forwards requests based on path mapping:

  • / to the frontend service.
  • /api to the backend service.
  • /dashboard to the custom target outside the landscape.
  1. The frontend and the backend communicate over private networking inside the landscape.