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/2021-07-01/cockpit.md
View File

@@ -5,4 +5,4 @@ quadrant: tools
featured: false
---
We decided to put this CMS on hold due to other - more adopted - alternatives like [Strapi](/tools/strapi.html).
We decided to put this CMS on hold due to other - more adopted - alternatives like [Strapi](/tools/strapi/).

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

@@ -7,7 +7,7 @@ tags: [coding, quality assurance, ci/cd]
The Conventional Commits specification is a lightweight convention on top of commit messages.
It provides a small set of rules for writing commit messages and therefore creating an explicit commit history.
The convention dovetails with [SemVer](/methods-and-patterns/semver2.html), by describing the features, fixes, and breaking changes made in commit messages.
The convention dovetails with [SemVer](/methods-and-patterns/semver2/), by describing the features, fixes, and breaking changes made in commit messages.
The specification contains only 16 items that are easy to follow. The predefined structure allows everyone in the team to get a better overview of what the commit messages relates to and what part of the code a change has to do with.
Some benefits of using these specifications include: the ability to automatically generate changelogs, the ability to determine a semantic version bump (based on the types of commits landed) and being able to communicate the nature of changes to teammates and stakeholders.

2
radar/2021-07-01/diagrams-as-code.md
View File

@@ -9,5 +9,5 @@ Documenting concepts and software architecture as diagrams using code offers gre
Having documentation and diagrams treated as code and checked-in into version control increases transparency, collaboration as well as productivity.
The textual representation of diagrams is easy to write and read. Generation of graphical representations as SVG or PNG images is also easy with the associated tools.
We make heavy use of [PlantUML](/tools/plant-uml.html) combined with [Asciidoc](/tools/asciidoc.html) and tools like [AsciiDoctor Diagram](https://asciidoctor.org/docs/asciidoctor-diagram/) to include and inline PlantUML diagrams into documentations.
We make heavy use of [PlantUML](/tools/plant-uml/) combined with [Asciidoc](/tools/asciidoc/) and tools like [AsciiDoctor Diagram](https://asciidoctor.org/docs/asciidoctor-diagram/) to include and inline PlantUML diagrams into documentations.
The latter allows a variety of other diagram formats which can be easily mixed and matched.

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

@@ -11,5 +11,5 @@ But Docker is also a complete production platform, where the capability to build
At the same time numerous alternate runtimes for containers – like containerd and podman – as well as image builders – like Kaniko and Buildah – have evolved during the last years.
Thanks to the standards established by the Open Container Initiative these tools are mostly interchangeable for the purposes of building and running containers.
To be more distinct, we now recommend using [Containers and Runtimes as specified by the Open Container Initiative](/platforms-and-aoe-services/oci-container.html).
To be more distinct, we now recommend using [Containers and Runtimes as specified by the Open Container Initiative](/platforms-and-aoe-services/oci-container/).
Docker is one of many tools to achieve that.

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

@@ -10,4 +10,4 @@ It has a huge community, so it's no wonder it's among the top 10 CMS worldwide i
At AOE we consume Drupal mainly headless via JSON API. We appreciate its large feature set and mature plugin system as well as the general ecosystem.
In addition, the extensive documentation and setup with [DDEV](/tools/ddev.html) make it easy to get started.
In addition, the extensive documentation and setup with [DDEV](/tools/ddev/) make it easy to get started.

4
radar/2021-07-01/eks.md
View File

@@ -9,8 +9,8 @@ tags: [devops]
Amazon EKS runs Kubernetes control plane instances across multiple Availability Zones to ensure high availability.
It also provides automated version upgrades and patching for them.
Amazon EKS is fully supported by [Terraform](https://www.aoe.com/techradar/platforms-and-aoe-services/terraform.html) which brings the advantage that its configuration is written in code,
which fulfils the [infrastructure as code](https://www.aoe.com/techradar/platforms-and-aoe-services/infrastructure-as-code.html) philosophy.
Amazon EKS is fully supported by [Terraform](/platforms-and-aoe-services/terraform/) which brings the advantage that its configuration is written in code,
which fulfils the [infrastructure as code](/platforms-and-aoe-services/infrastructure-as-code/) philosophy.
Amazon has also implemented important (security) features to their service to ensure that Amazon EKS is well integrated into the broader AWS landscape.
Kubernetes version upgrades and security patches are provided in a reliable schedule and with proper documentation.
Alongside with the managed service, Amazons also provides its own [EKS distribution](https://aws.amazon.com/de/blogs/opensource/introducing-amazon-eks-distro/) which closes the gap for on-premise installations.

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

@@ -7,6 +7,6 @@ featured: false
"Apache Kafka is an open-source distributed event streaming platform used by thousands of companies for high-performance data pipelines, streaming analytics, data integration, and mission-critical applications." (See http://kafka.apache.org/)
In comparison with other messaging solutions (such as [RabbitMQ](/tools/rabbitmq.html) - Apacha Kafka persist the messages (instead of routing them to subscribers). It is written in Scala and Java, and follows the idea of a “distributed log” where messages are appended to the end (like in a log) - and that log is persisted to disk. Clients can choose where they begin reading from that log - often Kafka Streams is used for this.
In comparison with other messaging solutions (such as [RabbitMQ](/tools/rabbitmq/) - Apacha Kafka persist the messages (instead of routing them to subscribers). It is written in Scala and Java, and follows the idea of a “distributed log” where messages are appended to the end (like in a log) - and that log is persisted to disk. Clients can choose where they begin reading from that log - often Kafka Streams is used for this.
We are using Kafka in data heavy projects - for example in data analytics use cases.

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

@@ -8,7 +8,7 @@ featured: true
[Nx](https://nx.dev/) is a suite of powerful, extensible dev tools to help you architect, test, and build at any scale.
It is mainly applicable in the environment of React, Angular and Node.js and tries to simplify and streamline the work in a mono repo.
At AOE, we are currently taking our first steps with NX in a mono repo that is home to both our React and Next.js based frontend and our [Go](/languages-and-frameworks/go-lang.html) / [Flamingo](/languages-and-frameworks/flamingo.html) based backend.
At AOE, we are currently taking our first steps with NX in a mono repo that is home to both our React and Next.js based frontend and our [Go](/languages-and-frameworks/go-lang/) / [Flamingo](/languages-and-frameworks/flamingo/) based backend.
The integration with the Node.js components (React, Next.js, Cypress) works smoothly and brings the expected benefits such as faster build times through intelligent caching.
Support for Go is currently only rudimentary, which is why NX still has to prove itself in this area.

2
radar/2021-07-01/oci-container.md
View File

@@ -13,6 +13,6 @@ In a DevOps environment, this helps a lot as we can run the exact same software
In a CI environment building the containers allows us to package and test the whole environment instead of different software components on different runtimes in a much more stable way.
Backed by services such as [Kubernetes](/platforms-and-aoe-services/kubernetes.html) and [Helm](/platforms-and-aoe-services/helm.html), we can deploy containers on a flexible infrastructure and enable our developers to test their software more easily in different environments.
Backed by services such as [Kubernetes](/platforms-and-aoe-services/kubernetes/) and [Helm](/platforms-and-aoe-services/helm/), we can deploy containers on a flexible infrastructure and enable our developers to test their software more easily in different environments.
Here at AOE, we use containers in different projects to become more flexible and faster, which increases our focus on development of even better and more stable software.

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

@@ -12,7 +12,7 @@ Compared to other monitoring systems it stands out in its simple, still powerful
Prometheus integrates very well with Grafana which is our tool of choice for dashboard visualization.
Through the [Prometheus Operator](https://github.com/prometheus-operator/prometheus-operator) project, the monitoring system can be configured through Kubernetes custom resource definitions.
These can be shipped by development teams alongside with their application deployments and allow [sharing responsibility](https://www.aoe.com/techradar/methods-and-patterns/shared-responsibility.html) for monitoring tasks between operations and engineering teams with a clear interface.
These can be shipped by development teams alongside with their application deployments and allow [sharing responsibility](/methods-and-patterns/shared-responsibility/) for monitoring tasks between operations and engineering teams with a clear interface.
With [Cortex](https://cortexmetrics.io/) and [Thanos](https://thanos.io/) the Prometheus-ecosystem knows two well-settled solutions for high-availability of the underlying time series database and with [Amazon Managed Services for Prometheus](https://aws.amazon.com/en/prometheus/) there's also a SaaS-Solution available.

8
radar/2021-07-01/state-management-pattern.md
View File

@@ -6,11 +6,11 @@ tags: [architecture, coding]
---
State Management is a design pattern with the goal of properly sharing state data across components and separating domain representation from state management.
This pattern is applied by many popular web frameworks such as [Vuex](/languages-and-frameworks/vuex.html), [Redux](/languages-and-frameworks/redux.html) or [Flux](/methods-and-patterns/flux.html).
This pattern is applied by many popular web frameworks such as [Vuex](/languages-and-frameworks/vuex/), [Redux](/languages-and-frameworks/redux/) or [Flux](/methods-and-patterns/flux/).
Especially in [reactive](/methods-and-patterns/reactive-programming.html) systems, this pattern helps to solve the task of maintaining decoupled, stateless components with immutable data.
Especially in [reactive](/methods-and-patterns/reactive-programming/) systems, this pattern helps to solve the task of maintaining decoupled, stateless components with immutable data.
The ways of implementing state management differs and depends on the specific requirements of the application at hand.
For distributed backend systems one might want to utilize [Akka's](/languages-and-frameworks/akka.html) cluster sharding module to elastically manage domain object states.
For distributed backend systems one might want to utilize [Akka's](/languages-and-frameworks/akka/) cluster sharding module to elastically manage domain object states.
We use the various state management patterns across most [Vue](/languages-and-frameworks/vue.html) and [React](/languages-and-frameworks/react.html) projects that warrant them.
We use the various state management patterns across most [Vue](/languages-and-frameworks/vue/) and [React](/languages-and-frameworks/react/) projects that warrant them.

4
radar/2021-07-01/strapi.md
View File

@@ -8,8 +8,8 @@ tags: [frontend]
Strapi is a headless CMS built with Javascript on Node.js.
Its data-centered approach offers great flexibility for many use cases by integrating with the available APIs.
Strapi's API comes in a RESTful and [GraphQL](/methods-and-patterns/graphql.html) variant.
Both perfectly support the [API-first design approach](/methods-and-patterns/api-first-design-approach.html).
Strapi's API comes in a RESTful and [GraphQL](/methods-and-patterns/graphql/) variant.
Both perfectly support the [API-first design approach](/methods-and-patterns/api-first-design-approach/).
Ever since the stable release version 3.0.0 from mid-2020, the CMS reached market maturity and offers a good choice for scalable headless CMSs.
As of the 3.6 release in April 2021, Strapi features [full internationalization support](https://strapi.io/blog/announcing-content-internationalization-v3-6), making it a viable candidate to be evaluated toe to toe with solutions like Drupal.