Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Visualisation of bounded context #40

Open
selketjah opened this issue Dec 8, 2022 · 7 comments
Open

Visualisation of bounded context #40

selketjah opened this issue Dec 8, 2022 · 7 comments

Comments

@selketjah
Copy link

Right now, we are using clouds to visualize a bounded context. We say it is an explicit boundary, but clouds represent fuzziness.

I started using squircles (rectangle with round corners) to represent BC's because I feel this fits better with what a bounded context is. (well defined, but at the boundaries still a bit rounded sometimes)
Any objections to this change?

@NTCoding
Copy link
Member

It's a fair question, and I would say anyone is free to use whatever notation they prefer as there is no standard.

With this canvas and message flow modelling I'm using the cloud because I think it looks good visually, I also use it to arbitrarily to represent subdomain / microservice / component / bounded context whatever terminology a particular client uses to describe their org/arch (in truth I don't even use the bounded context terminology anymore).

Regarding the main point here: should we update the documentation in this repo to use rounded rectangles instead of clouds? Personally I don't mind either way. Unless anyone thinks it's a bad idea then I would say go ahead and do it.

@yellowbrickc
Copy link
Contributor

I have a hard time to give an opinion without seeing your version, @selketjah. Could you add a picture here, please?

@cjjohansen
Copy link

To be honest. I intuitively think of external system or cloud when seeing a cloud widget. So I aggree with @selketjah. Personallly I would just draw an elipsis to reperesent a bounded context :-)

@AlexZeitler
Copy link
Contributor

AlexZeitler commented Feb 9, 2023

I also tend to agree with @selketjah.

Maybe have some dashed border as an fence analogy:

image

@selketjah
Copy link
Author

I have a hard time to give an opinion without seeing your version, @selketjah. Could you add a picture here, please?

Screenshot 2023-02-10 at 08 14 50

@yellowbrickc
Copy link
Contributor

Now I can see what you mean, thanks, @selketjah! I am so used to the cloud icon (and I like that it has a lot of touchpoints on all sides), that I have no clue if "it is better or worse", but I am surely not against your proposal.
Like @NTCoding said, "Unless anyone thinks it's a bad idea, then I would say go ahead and do it." 👍

@NTCoding
Copy link
Member

Looks pretty good to me, even nicer than the clouds. So from a visual perspective, it's a winner. In this form, I don't think it looks like too formal, either.

The argument that people associate a cloud with software running in the cloud was also something that made me see things a bit differently.

Well done @selketjah, and good luck with your homework 😆.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants