Configuring a Service Map
  • 06 Apr 2022
  • 2 Minutes to read
  • Contributors
  • Dark
    Light
  • PDF

Configuring a Service Map

  • Dark
    Light
  • PDF

Business scenario

Consider an E-Commerce solution is managed through Serverless360. Here, the resources that constitute order processing business flow are grouped in a Business Application.

The architecture of this business flow is as follows:

  1. Customer submits an order request in the Web App (Azure App Service).

  2. A Service Bus Message is triggered for every order placed (Service Bus Queue).

  3. A Logic App with Service Bus Queue trigger picks up the order message to execute the order (Logic App).

  4. An Azure Function invoked by the Logic app validates the order message for necessary details (Azure Function).

  5. After the successful validation, the message is forwarded to a Service Bus Topic for further processing (Service Bus Topic).

  6. An Azure Worker role listens to messages in Topic Subscriptions (Cloud Service).

  7. The message details are forwarded to a Storage Queue for Shipment follow up (Storage Queue).

  8. Another copy of the message is written in SQL database (SQL).

This architecture can be better understood in a pictorial representation.

Building a service map within the Business Application would be of real help for understanding this better.

Service map scenario.png

Bringing resources to the board

  • To get started, click the Add Service Map button in the Service Map section of any Business Application and give it a name.

  • In the Service Map section of the Business Application, the resources associated with the Business Application are listed in the left side menu.

  • The required resources can be selected from the left section (palette), which will add the representation of the resource in the right section (diagram pane).

Connecting the resources

  • A connection can be made between the resources by clicking and dragging from the edges of the representation.

  • Click and drag the resource icon in the centre to move it within the Service map diagram.

Connecting resources.gif

  • The resources will be presented in the board with the current monitoring state once the diagram is saved.

Grouping & Ungrouping

  • By using the Grouping option, users can easily group the necessary resources to build an inner level of orchestration in the service map architecture and track the health status of those grouped resources.
    The group name can be customized according to users' preferences.

  • When it is possible to group the Resource icons, it is also possible to ungroup the same. The Ungroup option is available to ungroup the Resource icons while editing the Service map architecture.

Grouping and Ungrouping.gif

Set as default

  • When there are more than one diagram, it is possible to make any desired diagram as default, which will always be displayed in the diagram section whenever entering Service Map section.

  • A Service Map can be marked as default by selecting it from the Actions dropdown.

  • The diagram section will display the diagram that has been set as the default.

Set as Default.png

Editing a Service Map

  • The Edit option under Actions dropdown can be used to modify the Service Map's architecture flow and name. The monitoring state of the connected resources is hidden when the user is in Edit mode.

Service Map Edit.png

Deleting a Service Map

  • A Service Map flow can be easily deleted with the help of Delete option under Actions dropdown.

Service Map delete.png

Downloading a Service Map

  • The Download option under Actions dropdown now allows users to download their Service Maps and store it offline for any further references.

  • The Service Map will be saved in SVG format for offline use.

Service map download.png


Was this article helpful?