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/2019-11-01/anypoint-platform.md
View File

@@ -5,4 +5,4 @@ quadrant: tools
featured: false
---
Recently our teams migrated some project from Anypoint to ["Apache Camel"](/tools/apache-camel.html) or use ["Alpakka"](/tools/alpakka.html) for integration work.
Recently our teams migrated some project from Anypoint to ["Apache Camel"](/languages-and-frameworks/apache-camel/) or use ["Alpakka"](/languages-and-frameworks/alpakka/) for integration work.

2
radar/2019-11-01/container-based-builds.md
View File

@@ -4,4 +4,4 @@ ring: adopt
quadrant: methods-and-patterns
---
Updated to "adopt". Container based builds has getting to the de facto standard for our pipelines in [GitLab](/tools/gitlab.html) or other CI Tools.
Updated to "adopt". Container based builds has getting to the de facto standard for our pipelines in [GitLab](/tools/gitlab/) or other CI Tools.

2
radar/2019-11-01/distributed-tracing.md
View File

@@ -8,4 +8,4 @@ tags: [devops]
Distributed Tracing creates visibility over processes spanning multiple applications.
In a microservice world where a request or operation involves multiple applications it is helpful to have an overview of what system is involved, at what point.
Also, visibility of communicated data and errors helps to quickly identify issues in a microservice environment.
Our tool of choice is [Jaeger](/platforms-and-aoe-services/jaeger.html) with [B3 Propagation](https://github.com/openzipkin/b3-propagation).
Our tool of choice is [Jaeger](/platforms-and-aoe-services/jaeger/) with [B3 Propagation](https://github.com/openzipkin/b3-propagation).

2
radar/2019-11-01/flamingo.md
View File

@@ -32,7 +32,7 @@ Flamingo has a clean architecture with clear dependencies in mind and offers a t
* GraphQL support and therefore support to build nice SPA and PWAs on top of it
* Resilience and Caching for external APIs calls.
Flamingo itself does not contain ORM Mapper or libraries - instead it emphasizes ["ports and adapters"](/methods-and-patterns/ports-and-adapters.html) architecture - so that you have a technology free (domain) model and any possible (and replaceable) persistence behind it.
Flamingo itself does not contain ORM Mapper or libraries - instead it emphasizes ["ports and adapters"](/methods-and-patterns/ports-and-adapters/) architecture - so that you have a technology free (domain) model and any possible (and replaceable) persistence behind it.
That makes Flamingo useful to build microservices and applications - especially to build "frontends" or portals that require interaction with other (micro) services in a distributed architecture.
When sticking to the architectural recommendation, you can build modular applications with replaceable adapters that gives you independent testability.

2
radar/2019-11-01/gitlab.md
View File

@@ -5,4 +5,4 @@ quadrant: tools
---
Moved to "adopt": GitLab has proven to be a very useful tool for code and the collaboration around it.
With [GitLab CI](/tools/gitlab-ci.html) there is also a powerful tool to automate continuous integration and delivery.
With [GitLab CI](/tools/gitlab-ci/) there is also a powerful tool to automate continuous integration and delivery.

4
radar/2019-11-01/graphql.md
View File

@@ -18,8 +18,8 @@ Key advantages are:
- the client (browser) controls what data should be sent (data reduction)
- with one request you can fetch "all" required data
Client side integration can be achieved using the [Apollo Client Framework](/tools/apollo-client.html) which easily
integrates into [React.js](/languages-and-frameworks/react.html) based frontends.
Client side integration can be achieved using the [Apollo Client Framework](/tools/apollo-client/) which easily
integrates into [React.js](/languages-and-frameworks/react/) based frontends.
The Flamingo framework [offers support for GraphQL](https://docs.flamingo.me/3.%20Flamingo%20Modules/graphql.html)
while Flamingo Commerce provides a full-featured GraphQL API for e-commerce:

2
radar/2019-11-01/jaeger.md
View File

@@ -4,7 +4,7 @@ ring: trial
quadrant: platforms-and-aoe-services
---
[Jaeger](https://www.jaegertracing.io/) is a tool for [Distributed Tracing](/platforms-and-aoe-services/distributed-tracing.html).
[Jaeger](https://www.jaegertracing.io/) is a tool for [Distributed Tracing](/platforms-and-aoe-services/distributed-tracing/).
Developed at Uber and inspired by Dapper and OpenZipkin it grew into an [Cloud Native Computing Foundation](https://www.cncf.io/) project.
Jaeger is a great tool for troubleshooting distributed systems, such as microservice architectures.

2
radar/2019-11-01/packer.md
View File

@@ -13,4 +13,4 @@ Another benefit is, that machine images can be tested to verify if they are work
Packer supports multiple cloud providers like AWS, GCP, Digital Ocean etc.
Machine images are important for modern deployment pipelines and fast ramp of new infrastructure.
We are using Packer to build so-called "Golden images" that are used in our [Infrastructure as Code](/methods-and-patterns/infrastructure-as-code.html) based provisionings.
We are using Packer to build so-called "Golden images" that are used in our [Infrastructure as Code](/platforms-and-aoe-services/infrastructure-as-code/) based provisionings.

2
radar/2019-11-01/raml.md
View File

@@ -4,6 +4,6 @@ ring: hold
quadrant: languages-and-frameworks
---
Since the RAML project has decided to [join](https://blogs.mulesoft.com/dev/api-dev/open-api-raml-better-together/) the OpenAPI initiative and the RAML ecosystem lacks further development and additional tools, we decided to use and recommend using ["OpenAPI specification (OAS)"](/tools/open-api.html) as description standard instead.
Since the RAML project has decided to [join](https://blogs.mulesoft.com/dev/api-dev/open-api-raml-better-together/) the OpenAPI initiative and the RAML ecosystem lacks further development and additional tools, we decided to use and recommend using ["OpenAPI specification (OAS)"](/tools/open-api/) as description standard instead.
RAML still provides advantages in modeling an API through it's more expressive modeling language and can produce OAS

2
radar/2019-11-01/zero-trust.md
View File

@@ -42,7 +42,7 @@ It involves many **areas and aspects**, including:
## Implementations
In 2009 Google implemented a zero trust architecture referred to as [BeyondCorp](https://cloud.google.com/beyondcorp). It utilizes OAuth and OpenID standards for implementing Authn and Authz, and has influenced the development of modern Zero Trust architectures.
Typical implementations involve using standards and tools for IAM and SSO, such as [Keycloak](/tools/keycloak.html).
Typical implementations involve using standards and tools for IAM and SSO, such as [Keycloak](/tools/keycloak/).
## Summary
While network segments and VPN connections may still be relevant in specific areas, AOE is increasingly implementing a Zero Trust approach in all solutions, components, and services.