How to set the Service Architectural Layer in Distributed Applications



Overview

In vFunction Server version 4.2, users can now manually set a Service Architectural Layer. This enhancement gives architects greater control over layering decisions. Architects can now manually assign services to specific architectural layers, overriding the AI-calculated layer assignments. Once a service is moved, TODOs are automatically recalculated based on the updated service layering, allowing teams to reflect intentional architectural decisions directly in the platform.

This capability works in the sub-systems graph, and not in the services graph, since internal sub-system layering is omitted from the todo calculation of the parent application.

Service Architectural Layer


Steps to set a Service Architectural Layer

  1. Log into the vFunction Server UI
  2. Select the desired Distributed App from the dropdown in the top, left corner next to the vFunction logo
  3. If none exists, create a Subsystem
  1. Click the Box Icon in the bottom of the center pane
  2. Drag a box around the desired subsystem of Services
  3. Ensure Create Subsystem is toggled on in the dialog box that launches
  4. Type the Subsystem’s name in the Name text box
  5. Click Save in the dialog box
  1. Click Subsystems in the top of the center pane
  2. Click-and-drag any Service from one horizontal pane to another. A dotted, red line will appear to indicate the current hierarchical layer. As you drag up or down, a new dotted, red line will appear to allow you to add the Service or Subsystem into a new hierarchical layer
  3. Click OK in the Subsystem Layers Modified dialog box