| Page Properties |
|---|
|
| Status | | Status |
|---|
| colour | Yellow |
|---|
| title | progress |
|---|
|
|
|---|
| Priority | 1 |
|---|
| Note |
|
|---|
| Assignee | Max, Inga |
|---|
Resources |
...
By chunking up the system into microservices it can be tough to keep the overview of all available services, their relationships and dependencies to each other. The following graphical overview of our microservice architecture offers you a first entry point into the yuuvis® Momentum landscape. By providing further and more detailed examples based on special use cases (flows) you'll get a better and easy way of understanding our entire landscape.
Graphical Overview
For visualizing the topology of our microservices the following overview shows - on a higher level - many of our core microservices.
For understanding various flows - on a more granular level - check out the detailed diagrams visualizing special use case.
Login to the Core API - Authentication (Browser / Application)
...
| Expand |
|---|
| title | Click here to show the content retrieval flow ( by ID ) >> |
|---|
|
| 1. - HTTP get request to object URL 2. - Enrichment of request with authentication Token 3. - Check for User Authorization using search service query 4. - Query elastic search for object ID 5. - Elasticsearch metadata reponse (if user is authorized) 6. - Repository url of objectId 7. - Request content of objectID 8. - Query objectId in Storage Provider 9. - Storage Provider metadata response 10. - Return metadata object metadata 11. - Write CONTENT_ACCESSED audit entry 12. - Create API response from metadata 13. - Return HTTP metadata response Webhook entry points *1 - dms.response.objects |
|
...
| Expand |
|---|
| title | Click here to show the content retrieval flow by ID (older version) >> |
|---|
|
| 1. - HTTP get request to object URL 2. - Enrichment of request with authentication Token 3. - Check for User Authorization using search service query 4. - Query elastic search for object ID 5. - Elasticsearch metadata reponse (if user is authorized) 6. - Verify that user has object access rights 7. - Retrieve metadata version using Registry Service 8. - Query object metadata version from database 9. - Return metadata including Repository URL of content 10. - Return content Repo URL 11. - Request content of objectID 12. - Query objectId in Storage Provider 13. - Storage Provider metadata response 14. - Return metadata object metadata 15. - Write CONTENT_ACCESSED audit entry 16. - Create API response from metadata 17. - Return HTTP metadata response Webhook entry points *1 - dms.response.objects |
|
...
| Expand |
|---|
| title | Click here to show the metadata retrieval flow ( by ID ) >> |
|---|
|
| 1. - HTTP get request to object URL 2. - Enrichment of request with authentication Token 3. - Request metadata 4. - Query objectId in database 5. - DB metadata response 6. - Write METADATA_ACCESSED audit entry 7. - Return metadata object metadata 8. - Create API response from metadata 9. - Return HTTP metadata response Webhook entry points *1 - dms.response.objects |
|
...
| Expand |
|---|
| title | Click here to show the metadata retrieval flow by ID (older version) >> |
|---|
|
| 1. - HTTP get request to object URL 2. - Enrichment of request with authentication Token 3. - Query Metadata availability using Search Service 4. - Query objectId in ES 5. - Elastic Search version data response 6. - Return registry link if user is authorized for to access the object 7. - Retrieve metadata version using Registry Service 8. - Retrieve object version from data base 9. - Database object metadata response 10. - Return metadata object metadata 11.- Write METADATA_ACCESSED audit entry 12. - Create API response from metadata 13. - Return HTTP metadata response Webhook entry points *1 - dms.response.objects |
|
...
| Info |
|---|
|
Read on
| Section |
|---|
| Column |
|---|
| Another Tutorial Brief summary of the article linked.
|
| Column |
|---|
| Another Concept Article Brief summary of the article linked. |
| Column |
|---|
| Another interesting Tutorial Brief summary of the article linked. |
|
|
