Outline architecture docs#142
Open
jabley wants to merge 7 commits into
Open
Conversation
jabley
force-pushed
the
feat/architecture-docs
branch
5 times, most recently
from
0f741c1 to
c45922f
Compare
Contributor
Author
|
Thanks @carlosmartinez, I'm happy for someone to take another pass at this. |
Make it explicit that the connection is established by an outbound connection from the relay listener inside the Trust network boundary.
Add `text` to blank markdown code blocks.
Table grumblings in markdown.
This looked wrong in my editor and wrong in GitHub, so I think this is an OK change.
I have a minor preference for this because it's more structured data.
This is what Git does when using the file backend, so it's could be mildly familiar to developers.
This is possibly a moving target but I wanted to get capture my understanding whilst preparing to take this to the Technical Review Group - https://architecture.digital.nhs.uk/trg
jabley
force-pushed
the
feat/architecture-docs
branch
from
c45922f to
9ad444a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
I need to take Rubie to the Technical Review Group, at this stage for information only. I want to cover the next 3 to 6 months of our proposed direction so that I'm not giving them small frequent updates - they're mainly concerned in significant deltas.
This work is noteworthy because of how we're intending to run software with a Trust's IT estate and we're keen to share our technique, get it critiqued and improved if possible.
I needed to get a better understanding of what we're proposing so I've added a bit more here. I'll also be updating the internal EA tooling with what we have but this repository is the source of truth for the team.
Jira link
None - I asked @carlosmartinez and was advised to just add this work as a PR.
Review notes
The commits should be reviewable in isolation.
There may be some inaccuracies which aren't addressed by this PR; eg
MPPS N-SETis not actually a thing yet because modalities.Review checklist