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

fix: update links and remove .html extension

Browse Source
This commit is contained in:
Mathias Schopmans
2024-03-12 11:42:36 +01:00
committed by Mathias Schopmans
parent bc1e5b2d70
commit daa86a3f59
75 changed files with 103 additions and 103 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
radar/2022-03-28/gitlab-ci.md
View File

@@ -5,4 +5,4 @@ quadrant: tools
featured: false
---
We merged "GitLab CI" and [GitLab](https://www.aoe.com/techradar/tools/gitlab.html)
We merged "GitLab CI" and [GitLab](/tools/gitlab/)

4
radar/2022-03-28/monorepo.md
View File

@@ -9,7 +9,7 @@ tags: [coding]
A monorepo is a single repository containing multiple projects and shared libraries with their relationships.
At AOE, we are using a monorepo that is home to both our React and Next.js based frontends and
our [Go](/languages-and-frameworks/go-lang.html) / [Flamingo](/languages-and-frameworks/flamingo.html) based backends,
our [Go](/languages-and-frameworks/go-lang/) / [Flamingo](/languages-and-frameworks/flamingo/) based backends,
as well as shared libraries we use in all of our projects.
The main benefits in that approach are:
@@ -19,4 +19,4 @@ The main benefits in that approach are:
* Tool consistency over all projects
If you take the monorepo approach, of course you want to have a tool to manage it. There are a lot of them on the market
and at AOE we have decided to go with [Nx](/tools/nx.html).
and at AOE we have decided to go with [Nx](/tools/nx/).

2
radar/2022-03-28/pipeline-as-code.md
View File

@@ -13,6 +13,6 @@ Continuous Integration and Delivery is an important part in every project. Pipel
now be handled like most other parts of your software. The pipeline configuration can run through lint checks, or a test
suite before the configuration is shared across teams in your organisation.
Using [container based builds](https://www.aoe.com/techradar/methods-and-patterns/container-based-builds.html) is now
Using [container based builds](/methods-and-patterns/container-based-builds/) is now
also the de facto standard. Combining these two techniques enables running isolated builds in an easily reproducible
environment so teams can get quick feedback on every change.

2
radar/2022-03-28/resilience-thinking.md
View File

@@ -19,7 +19,7 @@ patterns and methods used are:
* Detect errors explicitly: Check the response message format and configure proper timeouts for external communication
* Handle errors in a smart way: Show a nice error message to your customer or, even better, graceful degrade features -
e.g. by showing some fallback text
* Use message-based communication where useful ([Decoupling Infrastructure via Messaging](/methods-and-patterns/decoupling-infrastructure-via-messaging.html))
* Use message-based communication where useful ([Decoupling Infrastructure via Messaging](/methods-and-patterns/decoupling-infrastructure-via-messaging/))
* Use circuit breakers to isolate errors and allow systems to recover
* Use short activation paths in your strategic architecture - so that there is only a minimal set of communications
between your services required for certain features or business requests

4
radar/2022-03-28/sass.md
View File

@@ -7,8 +7,8 @@ featured: false
Since the heydays of Sass, the requirements for styling solutions have changed.
With modern solutions like [CSS-in-JS](/methods-and-patterns/css-in-js.html),
[Tailwind](/languages-and-frameworks/tailwindcss.html) or [PostCSS](/tools/postcss.html), you get scoped CSS out of the
With modern solutions like [CSS-in-JS](/methods-and-patterns/css-in-js/),
[Tailwind](/languages-and-frameworks/tailwindcss/) or [PostCSS](/tools/postcss/), you get scoped CSS out of the
box and can get rid of the manual and therefore error-prone BEM methodology. Furthermore, mapping class names to
elements is no longer necessary.

4
radar/2022-03-28/spring-rest-docs.md
View File

@@ -5,7 +5,7 @@ quadrant: tools
tags: [documentation]
---
[Spring REST Docs](https://spring.io/projects/spring-restdocs/) auto generates [Asciidoctor](http://asciidoctor.org/) snippets with the help of [Spring MVC Test](http://docs.spring.io/spring/docs/current/spring-framework-reference/htmlsingle#spring-mvc-test-framework) or [RestAssured](https://www.aoe.com/techradar/tools/rest-assured.html).
[Spring REST Docs](https://spring.io/projects/spring-restdocs/) auto generates [Asciidoctor](http://asciidoctor.org/) snippets with the help of [Spring MVC Test](http://docs.spring.io/spring/docs/current/spring-framework-reference/htmlsingle#spring-mvc-test-framework) or [RestAssured](/tools/rest-assured/).
So you can be sure that your tests are inline with the documentation.
We now use an Api First approach in conjunction with [Open API](https://www.aoe.com/techradar/tools/open-api.html). We see an active community there and a lot of support with this approach.
We now use an Api First approach in conjunction with [Open API](/tools/open-api/). We see an active community there and a lot of support with this approach.