architecture-beta - linking between points in different groups causing layout problems?

[chrissearle]

Not sure if this is due to architecture-beta still being in beta or if I am doing something wrong here.

Thought I'd just ask if I'm missing something obvious or not :)

---

I have the following (anonymised) setup:

architecture-beta
    group a(cloud)[Cloud Provider 1]
    group b(cloud)[Cloud Provider 2]
    group c(internet)[Public Web]
    
    service service1(server)[Service 1] in a
    service service2(server)[Service 2] in a
    service service3(server)[Service 3] in a
    service database1(database)[Database 1] in a

    service web1(server)[Web 1] in b

    service mob1(internet)[Mobile App 1] in c
    service mob2(internet)[Mobile App 2] in c

    junction j1 in a
    junction j2 in c

    service1:B -- T:database1
    service1:T -- B:j1
    service2:L -- R:j1
    service3:R -- L:j1

    j2:T -- B:mob1
    j2:B -- T:mob2

which looks like this:

architecture-beta
    group a(cloud)[Cloud Provider 1]
    group b(cloud)[Cloud Provider 2]
    group c(internet)[Public Web]
    
    service service1(server)[Service 1] in a
    service service2(server)[Service 2] in a
    service service3(server)[Service 3] in a
    service database1(database)[Database 1] in a

    service web1(server)[Web 1] in b

    service mob1(internet)[Mobile App 1] in c
    service mob2(internet)[Mobile App 2] in c

    junction j1 in a
    junction j2 in c

    service1:B -- T:database1
    service1:T -- B:j1
    service2:L -- R:j1
    service3:R -- L:j1

    j2:T -- B:mob1
    j2:B -- T:mob2

Loading

Service 1 is the main hub for everything - so I want to add two more links - one from web1 to service1 and one from j2 to service1.

If we add just web1:

    web1:L -- R:service1

then it moves group b inside group a:

architecture-beta
    group a(cloud)[Cloud Provider 1]
    group b(cloud)[Cloud Provider 2]
    group c(internet)[Public Web]
    
    service service1(server)[Service 1] in a
    service service2(server)[Service 2] in a
    service service3(server)[Service 3] in a
    service database1(database)[Database 1] in a

    service web1(server)[Web 1] in b

    service mob1(internet)[Mobile App 1] in c
    service mob2(internet)[Mobile App 2] in c

    junction j1 in a
    junction j2 in c

    service1:B -- T:database1
    service1:T -- B:j1
    service2:L -- R:j1
    service3:R -- L:j1

    j2:T -- B:mob1
    j2:B -- T:mob2
    
    web1:L -- R:service1

Loading

If I link just the junction in:

    service1:L -- R:j2

then it makes the entire thing extremely wide

architecture-beta
    group a(cloud)[Cloud Provider 1]
    group b(cloud)[Cloud Provider 2]
    group c(internet)[Public Web]
    
    service service1(server)[Service 1] in a
    service service2(server)[Service 2] in a
    service service3(server)[Service 3] in a
    service database1(database)[Database 1] in a

    service web1(server)[Web 1] in b

    service mob1(internet)[Mobile App 1] in c
    service mob2(internet)[Mobile App 2] in c

    junction j1 in a
    junction j2 in c

    service1:B -- T:database1
    service1:T -- B:j1
    service2:L -- R:j1
    service3:R -- L:j1

    j2:T -- B:mob1
    j2:B -- T:mob2
    
    service1:L -- R:j2

Loading

And if I add in both:

    web1:L -- R:service1
    service1:L -- R:j2

then its even wider and still overlaying groups:

architecture-beta
    group a(cloud)[Cloud Provider 1]
    group b(cloud)[Cloud Provider 2]
    group c(internet)[Public Web]
    
    service service1(server)[Service 1] in a
    service service2(server)[Service 2] in a
    service service3(server)[Service 3] in a
    service database1(database)[Database 1] in a

    service web1(server)[Web 1] in b

    service mob1(internet)[Mobile App 1] in c
    service mob2(internet)[Mobile App 2] in c

    junction j1 in a
    junction j2 in c

    service1:B -- T:database1
    service1:T -- B:j1
    service2:L -- R:j1
    service3:R -- L:j1

    j2:T -- B:mob1
    j2:B -- T:mob2
    
    web1:L -- R:service1
    service1:L -- R:j2

Loading