AJR/TechradarDev
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: fix internal links

Browse Source
This commit is contained in:
Stefan Rotsch
2024-06-26 10:56:44 +02:00
committed by Stefan Rotsch
parent 014cc8d360
commit 84d5939770
36 changed files with 43 additions and 49 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
radar/2021-07-01/loki.md
View File

@@ -5,7 +5,7 @@ quadrant: tools
tags: [devops]
---
Archiving indexed log data with a system like [Elasticsearch](../platforms-and-aoe-services/elasticsearch.html) can be expensive, and archiving it as simple text files makes it hard to query. [Loki](https://grafana.com/oss/loki/) solves this issue by adding a reference database based on [Kubernetes](../platforms-and-aoe-services/kubernetes.html) labels to each log line, similar to [Prometheus](../platforms-and-aoe-services/prometheus.html), but storing the log data inside a simple blob storage like AWS S3. This allows the user to query the data by predefined labels and keeps the costs for indexing low.
Archiving indexed log data with a system like [Elasticsearch](/platforms-and-aoe-services/elasticsearch/) can be expensive, and archiving it as simple text files makes it hard to query. [Loki](https://grafana.com/oss/loki/) solves this issue by adding a reference database based on [Kubernetes](/platforms-and-aoe-services/kubernetes/) labels to each log line, similar to [Prometheus](/platforms-and-aoe-services/prometheus/), but storing the log data inside a simple blob storage like AWS S3. This allows the user to query the data by predefined labels and keeps the costs for indexing low.
Another benefit is that Loki does not have an endpoint for mutating log data, making the data immutable from a potentially compromised system.

2
radar/2021-07-01/microfrontends.md
View File

@@ -8,4 +8,4 @@ tags: [architecture]
The Micro Frontends approach continues to prove to be a valuable pattern for large-scale systems developed by several teams.
Therefore, we moved this pattern to "adopt".
We use [page composing](methods-and-patterns/page-composing.html) as one implementation of this pattern.
We use [page composing](/methods-and-patterns/page-composing/) as one implementation of this pattern.

2
radar/2021-07-01/page-composing.md
View File

@@ -6,7 +6,7 @@ tags: [architecture]
---
Page composing is a way to aggregate multiple independent page fragments into one combined web page.
As an implementation of [Micro Frontends](methods-and-patterns/microfrontends.html), this approach supports to deploy and run services agnostic to the technologies used per team.
As an implementation of [Micro Frontends](/methods-and-patterns/microfrontends/), this approach supports to deploy and run services agnostic to the technologies used per team.
The concept builds upon the fact that all involved services deliver valid HTML as their output.
Our solution is a small application which takes care of gathering the page fragments from all services and composing each into a defined HTML template.