Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
opf-2021-ttc2070-core-template-v1
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
jamkit
project-templates
opf-2021-ttc2070-core-template-v1
Commits
44dbc15c
Commit
44dbc15c
authored
3 years ago
by
Marko Rintamäki
Browse files
Options
Downloads
Patches
Plain Diff
Update application-architecture.md
parent
048337d3
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Pipeline
#438996
passed
3 years ago
Stage: test
Stage: deploy
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/30-Architecture-and-design/application-architecture.md
+36
-2
36 additions, 2 deletions
docs/30-Architecture-and-design/application-architecture.md
with
36 additions
and
2 deletions
docs/30-Architecture-and-design/application-architecture.md
+
36
−
2
View file @
44dbc15c
...
@@ -119,10 +119,44 @@ In other words, how have those different environments been implemented in the pr
...
@@ -119,10 +119,44 @@ In other words, how have those different environments been implemented in the pr
*
Deployment diagram
*
Deployment diagram
## Database descriptions
## Database descriptions
(Databases as ER-diagram)
> When defining a service, it is common to describe the rough structure of the required data warehouse, eg in the form of an ER diagram.
This gives an idea of what kind of solution is needed. You can apply PlantUML description to generate an ER diagram.
ER-Scheme
**Example**
```
plantuml
' hide the spot
hide circle
' avoid problems with angled crows feet
skinparam linetype ortho
entity "Entity01" as e01 {
*e1_id : number <<generated>>
--
*name : text
description : text
}
entity "Entity02" as e02 {
*e2_id : number <<generated>>
--
*e1_id : number <<FK>>
other_details : text
}
entity "Entity03" as e03 {
*e3_id : number <<generated>>
--
*e1_id : number <<FK>>
other_details : text
}
e01 ||..o{ e02
e01 |o..o{ e03
```
##
##
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment