Skip to main content

Detailed text description: Landscape with a service as gateway

This page provides a long description of the diagram used in the Landscape Networking article. It shows a Landscape without a Workspace Router, where one of the services acts as the Landscape gateway.

Overview​

The diagram shows an app user above a single landscape deployment area. The landscape contains two services.

Main components​

  1. App user:
  • Positioned at the top, outside the landscape.
  • Sends requests to the application.
  1. Reactive service named frontend:
  • Is marked as the Landscape gateway.
  1. Reactive service named backend:
  • Has no connection to the outside of the landscape.

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 go directly to the frontend service, because it is the Landscape gateway. There is no Workspace Router in between.

  2. The frontend and the backend communicate over private internal hostnames. The backend is only reachable from inside the landscape.