Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

PlantUML Pleasantness: Keeping Elements Together

DZone's Guide to

PlantUML Pleasantness: Keeping Elements Together

PlantUML automatically lays out UML diagrams from a description. It's designed to avoid laying out the diagram manually, but it helps to know how to make it look nice.

· Integration Zone ·
Free Resource

The Future of Enterprise Integration: Learn how organizations are re-architecting their integration strategy with data-driven app integration for true digital transformation.

When we write a PlantUML definition, the generated graphical diagram is laid out by PlantUML. In a previous post, we learned how to move elements using the length of the connection. But we can also use a together block with all the elements that should be at the same level. PlantUML will try to keep the elements together when the diagram is drawn. 

In the following sample PlantUML definition, we want the PostgresDB and Mail elements to be at the same level, so we group them using a together block:

@startuml

actor User
[Third party application] as ThirdPartyApp

/' Try to keep PostgresDB and Mail together,
   so they are at the same level in the diagram. '/
together {
    [PostgreSQL database] as PostgresDB <<Database>>
    [Mail server] as Mail <<Mail server>>
}

package "Spring Boot Application" {
    [Controllers] <<Spring REST controllers>>
    [DataStoreService] <<Spring service>>
    [Repository] <<Spring repository>>
}

User --> Controllers
ThirdPartyApp --> Controllers

Controllers --> DataStoreService

DataStoreService --> Repository
DataStoreService --> Mail

Repository --> PostgresDB

@enduml

Let's create the diagram. We see that the elements are aligned nicely:

Written with PlantUML 8086.

Make your mark on the industry’s leading annual report. Fill out the State of API Integration 2019 Survey and receive $25 to the Cloud Elements store.

Topics:
integration ,uml ,diagrams

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}