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

Fix kafka to search flow in diagram #106

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

michquinn
Copy link
Contributor

Would close #105

Copy link
Contributor

@FlatBallFlyer FlatBallFlyer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ya - No - I get what you're saying, and the text is accurate, the visual rendering looses a pattern that should make it eaiser to see and understand the system as a whole. If we use a <--> connector the alignment of UI -> API -> Data in 3 columns looks right and the arrow-head on the BUS side is hidden by all the other arrows connecting inbound there.

If we want arrows to represent network connections, all arrows should go from bus to database. If we are using arrows to represent flow of data, then mongo database collections will sources, and elastic is a sink. This diagram is supposed to "look good" - the technical aspects of sources and sinks is in the architecture.yaml file. That probably does need to be updated, but I haven't looked at it in quite a while.

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

Successfully merging this pull request may close these issues.

Fix Architecture Diagram Search Flow
2 participants