Fix typos and change some grammatical constructions
This commit is contained in:
daniel.motzko
@@ -3,7 +3,6 @@ title: "Akka Streams"
|
||||
ring: adopt
|
||||
quadrant: languages-and-frameworks
|
||||
featured: false
|
||||
|
||||
---
|
||||
|
||||
Updated to "adopt"
|
||||
@@ -2,7 +2,6 @@
|
||||
title: "Alpakka"
|
||||
ring: adopt
|
||||
quadrant: languages-and-frameworks
|
||||
|
||||
---
|
||||
|
||||
Updated to "adopt"
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: "Anypoint platform"
|
||||
title: "Anypoint Platform"
|
||||
ring: trial
|
||||
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"](/tools/apache-camel.html) or use ["Alpakka"](/tools/alpakka.html) for integration work.
|
||||
@@ -2,8 +2,8 @@
|
||||
title: "AOE SSO"
|
||||
ring: adopt
|
||||
quadrant: platforms-and-aoe-services
|
||||
|
||||
---
|
||||
|
||||
To improve security and user experience we decided to install an organisation wide SSO and use OpenID Connect integrate with existing tools.
|
||||
We use [Keycloak](/tools/keycloak.html) as the SSO server, which is backed by our LDAP.
|
||||
This also helps to implement new infrastructure security based on ["BeyondCorp"](/methods-and-patterns/beyondcorp.html).
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: "Apollo Client"
|
||||
ring: trial
|
||||
quadrant: tools
|
||||
|
||||
---
|
||||
|
||||
The [Apollo Client](https://github.com/apollographql/apollo-client) is a tool to efficiently work together with an GraphQL server.
|
||||
|
||||
@@ -2,11 +2,10 @@
|
||||
title: "ZeroTrust"
|
||||
ring: trial
|
||||
quadrant: methods-and-patterns
|
||||
|
||||
---
|
||||
|
||||
ZeroTrust is a paradigm where no trust is assumed inside a known network, frameworks such as Google's BeyondCorp are build upon that pattern.
|
||||
With the surge of cloud technologies and micro services the network perimeter is ever disappearing.
|
||||
With the surge of cloud technologies and microservices the network perimeter is ever disappearing.
|
||||
This provides challenges for authentication of subjects that used to heavily rely on network segments.
|
||||
With Zero Trust no assumption is made about how far something can be trusted, everything is untrusted by default and authentication and authorisation happens all the time, not just once.
|
||||
While network segments and VPN connections may still have relevance in specific areas AOE is increasingly implementing BeyondCorp in all its components and services with implementing OAuth and OpenID Connect.
|
||||
|
||||
@@ -2,6 +2,6 @@
|
||||
title: "Cockpit"
|
||||
ring: assess
|
||||
quadrant: tools
|
||||
|
||||
---
|
||||
|
||||
[Cockpit](https://getcockpit.com/) is a self-hosted headless and api-driven content management system.
|
||||
@@ -2,7 +2,6 @@
|
||||
title: "Concourse"
|
||||
ring: trial
|
||||
quadrant: tools
|
||||
|
||||
---
|
||||
|
||||
[Concourse](https://concourse-ci.org/) is an open-source continuous "thing-doer". It represents a general approach for automation which can be used for Continuous Integration and Continuous Delivery. Concourse CI follows a strict concept that is based on idempotency, immutability, declarative config, stateless workers, and reproducible builds. Pipelines are built on the mechanics of resources, tasks and jobs, which are all configured in one or multiple YAML files.
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: "Container-based builds"
|
||||
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.
|
||||
@@ -2,9 +2,9 @@
|
||||
title: "Cypress"
|
||||
ring: assess
|
||||
quadrant: tools
|
||||
|
||||
---
|
||||
[Cypress](https://www.cypress.io/) is a new front-end testing tool (E2E). It comes as a simple node package and is therefore easy to use and maintain for front-end developers and testers. Cypress has a different approach than Selenium. It runs in the browser and in the same loop as the device under test.
|
||||
|
||||
[Cypress](https://www.cypress.io/) is a front-end testing tool (E2E). It comes as a simple node package and is therefore easy to use and maintain for front-end developers and testers. Cypress has a different approach than Selenium. It runs in the browser and in the same loop as the device under test.
|
||||
|
||||
Good:
|
||||
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: "Dependency Update Scan"
|
||||
ring: assess
|
||||
quadrant: methods-and-patterns
|
||||
|
||||
---
|
||||
|
||||
Automated dependency scans are useful to remove the manual task of regularly checking for version updates.
|
||||
|
||||
@@ -2,10 +2,9 @@
|
||||
title: "Distributed Tracing"
|
||||
ring: trial
|
||||
quadrant: platforms-and-aoe-services
|
||||
|
||||
---
|
||||
|
||||
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.
|
||||
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).
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: "Amazon EKS"
|
||||
ring: trial
|
||||
quadrant: platforms-and-aoe-services
|
||||
|
||||
---
|
||||
|
||||
[Amazon Elastic Kubernetes Service](https://aws.amazon.com/de/eks/) (Amazon EKS) is a managed service that makes it easy for you to run Kubernetes on AWS without needing to stand up or maintain your own Kubernetes control plane.
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: "Event Storming"
|
||||
ring: assess
|
||||
quadrant: methods-and-patterns
|
||||
|
||||
---
|
||||
|
||||
Event Storming is a method of modeling business processes using domain events.
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: "Falco"
|
||||
ring: assess
|
||||
quadrant: tools
|
||||
|
||||
---
|
||||
|
||||
Falco is an open source project for intrusion and abnormality detection for Cloud Native platforms such as Kubernetes.
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: "Flamingo"
|
||||
ring: adopt
|
||||
quadrant: languages-and-frameworks
|
||||
|
||||
---
|
||||
|
||||
Flamingo is a high productivity go based framework for rapidly building fast and pluggable web projects.
|
||||
@@ -25,7 +24,7 @@ Flamingo has a clean architecture with clear dependencies in mind and offers a t
|
||||
* Authentication concepts and security middleware
|
||||
* Flexible routing with support for prefix routes and reverse routing
|
||||
* Web Controller Support with: Request / Response / Form Handling etc
|
||||
* Operational Readyness: Logging, (distributed) Tracing, Metrics and Healthchecks with separate endpoint
|
||||
* Operational Readiness: Logging, (distributed) Tracing, Metrics and Healthchecks with separate endpoint
|
||||
* Localisation
|
||||
* Commands
|
||||
* Session Handling and Management
|
||||
@@ -34,6 +33,6 @@ Flamingo has a clean architecture with clear dependencies in mind and offers a t
|
||||
|
||||
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.
|
||||
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.
|
||||
When sticking to the architectural recommendation, you can build modular applications with replaceable adapters that gives you independent testability.
|
||||
|
||||
With **"Flamingo Commerce"** there is an additional active projects that offer rich and flexible features to build modern e-commerce applications.
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: "Flow"
|
||||
ring: assess
|
||||
quadrant: tools
|
||||
|
||||
---
|
||||
|
||||
[Flow](https://flow.org/) is a static type checker for JavaScript code. Its goal is to make code faster, smarter,
|
||||
more confidently, and to a bigger scale.
|
||||
@@ -2,8 +2,7 @@
|
||||
title: "Flux"
|
||||
ring: assess
|
||||
quadrant: methods-and-patterns
|
||||
|
||||
---
|
||||
|
||||
[Flux](https://facebook.github.io/flux/) is an application architecture for building client-side web applications,
|
||||
which is based on React's composable view components.
|
||||
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
title: "GitFlow"
|
||||
ring: hold
|
||||
quadrant: methods-and-patterns
|
||||
|
||||
---
|
||||
|
||||
Ever since there are recurring discussions about the version control strategy that a team should use.
|
||||
|
||||
We have also made the experience when new teams start off with using blocking or long-lived feature branches (merge late once all review comments are done) it has a negative impact on team performance.
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: "Go / Golang"
|
||||
ring: adopt
|
||||
quadrant: languages-and-frameworks
|
||||
|
||||
---
|
||||
|
||||
We have moved Go to "adopt".
|
||||
@@ -2,7 +2,6 @@
|
||||
title: "GraphQL"
|
||||
ring: adopt
|
||||
quadrant: methods-and-patterns
|
||||
|
||||
---
|
||||
|
||||
GraphQL is a query language for your API, and a server-side runtime for executing queries by using a type system you define for your data. GraphQL isn't tied to any specific database or storage engine and is instead backed by your existing code and data.
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: "Groovy"
|
||||
ring: hold
|
||||
quadrant: languages-and-frameworks
|
||||
|
||||
---
|
||||
|
||||
Since the rise of Kotlin, we seen no need why to still use Groovy as an alternative to Java running on the JVM.
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: "GRPC"
|
||||
ring: adopt
|
||||
quadrant: languages-and-frameworks
|
||||
|
||||
---
|
||||
|
||||
We adopted GRPC, because it is used on multiple places within our microservice oriented architectures for internal communication.
|
||||
@@ -5,4 +5,5 @@ quadrant: methods-and-patterns
|
||||
featured: false
|
||||
---
|
||||
|
||||
We use HAL in cases where we need to link resources in payloads. HATEOAS has not proven to be very useful in our projects.
|
||||
We use HAL in cases where we need to link resources in payloads.
|
||||
HATEOAS has not proven to be very useful in our projects.
|
||||
@@ -2,8 +2,6 @@
|
||||
title: "Helm"
|
||||
ring: trial
|
||||
quadrant: platforms-and-aoe-services
|
||||
|
||||
---
|
||||
[Helm](https://helm.sh/) is a package manager for [Kubernetes](https://kubernetes.io/), which simplifies the deployment
|
||||
of applications into a Kubernetes cluster and provides additional features like e.g. versioning and rollbacks.
|
||||
|
||||
[Helm](https://helm.sh/) is a package manager for [Kubernetes](https://kubernetes.io/), which simplifies the deployment of applications into a Kubernetes cluster and provides additional features like e.g. versioning and rollbacks.
|
||||
|
||||
@@ -5,4 +5,4 @@ quadrant: tools
|
||||
featured: false
|
||||
---
|
||||
|
||||
Hystrix is not actively maintained anymore and some of its goals can now be handled with service meshs.
|
||||
Hystrix is not longer actively maintained and some of its goals can now be handled with service meshs.
|
||||
@@ -2,7 +2,6 @@
|
||||
title: "Infrastructure as Code"
|
||||
ring: adopt
|
||||
quadrant: platforms-and-aoe-services
|
||||
|
||||
---
|
||||
|
||||
Updated to "adopt"
|
||||
@@ -2,7 +2,6 @@
|
||||
title: "Jaeger"
|
||||
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). Developed at Uber and inspired by Dapper and OpenZipkin it grew into an [Cloud Native Computing Foundation](https://www.cncf.io/) project.
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: "Kotlin"
|
||||
ring: adopt
|
||||
quadrant: languages-and-frameworks
|
||||
|
||||
---
|
||||
|
||||
Kotlin is used successfully in production by multiple teams.
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: "Next.js"
|
||||
ring: trial
|
||||
quadrant: languages-and-frameworks
|
||||
|
||||
---
|
||||
|
||||
[Next.js](https://nextjs.org/) is a JavaScript and React based framework which makes use of server side rendering.
|
||||
@@ -2,7 +2,6 @@
|
||||
title: "Open API"
|
||||
ring: adopt
|
||||
quadrant: tools
|
||||
|
||||
---
|
||||
|
||||
The OpenAPI Specification is becoming a broadly adopted industry standard for describing modern REST APIs. Other initiatives like RAML have [joined](https://blogs.mulesoft.com/dev/api-dev/open-api-raml-better-together/) the OpenAPI Initiative.
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: "Packer"
|
||||
ring: adopt
|
||||
quadrant: platforms-and-aoe-services
|
||||
|
||||
---
|
||||
|
||||
[Hashicorp Packer](https://www.packer.io/intro/getting-started/build-image.html) is a lightweight tool which automates the creation of any type of machine images (Machine Image As A Code) for multiple platforms.
|
||||
@@ -13,5 +12,5 @@ Packer only builds images. But once you have them you can deploy your infrastruc
|
||||
Another benefit is, that machine images can be tested to verify if they are working correctly.
|
||||
Packer supports multiple cloud providers like AWS, GCP, Digital Ocean etc.
|
||||
|
||||
Machine images are important for modern deployment pipelines and fast ramp of 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.
|
||||
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.
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: "Plant UML"
|
||||
ring: trial
|
||||
quadrant: tools
|
||||
|
||||
---
|
||||
|
||||
[PlantUML](https://plantuml.com/) is an open source project that allows to create UML diagrams in a text-based and declarative way.
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: "Ports and Adapters"
|
||||
ring: adopt
|
||||
quadrant: methods-and-patterns
|
||||
|
||||
---
|
||||
|
||||
Updated to "adopt"
|
||||
@@ -4,7 +4,9 @@ ring: trial
|
||||
quadrant: tools
|
||||
featured: false
|
||||
---
|
||||
[Postman](https://www.getpostman.com/) is an API testing and documentation tool. Requests can be bundled into folders
|
||||
and easily be configured to be executed against multiple environments. Responses can be evaluated using the "test" feature.
|
||||
|
||||
[Postman](https://www.getpostman.com/) is an API testing and documentation tool.
|
||||
Requests can be bundled into folders and easily be configured to be executed against multiple environments.
|
||||
Responses can be evaluated using the "test" feature.
|
||||
|
||||
Even automated testing is possible using [Newman](https://www.npmjs.com/package/newman) as an addition to Postman.
|
||||
@@ -2,6 +2,6 @@
|
||||
title: "RabbitMQ"
|
||||
ring: adopt
|
||||
quadrant: tools
|
||||
|
||||
---
|
||||
|
||||
RabbitMQ has proven to work very well for messaging in our projects, that is why we updated it to "adopt".
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: "RAML"
|
||||
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.
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: "Reactive Programming"
|
||||
ring: adopt
|
||||
quadrant: methods-and-patterns
|
||||
|
||||
---
|
||||
|
||||
The reactive style of programming promotes event-based thinking and modeling --
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: "Self-Service Infrastructure"
|
||||
ring: trial
|
||||
quadrant: platforms-and-aoe-services
|
||||
|
||||
---
|
||||
|
||||
Moved to "trial".
|
||||
@@ -2,7 +2,6 @@
|
||||
title: "SonarQube"
|
||||
ring: trial
|
||||
quadrant: tools
|
||||
|
||||
---
|
||||
|
||||
At AOE, we are using SonarQube to get a historical overview of the code quality in our Projects. With SonarQube, you can get a quick insight into the condition of your code. It analyzes many languages and provides numerous static analysis rules.
|
||||
|
||||
@@ -2,9 +2,6 @@
|
||||
title: "Spring Boot"
|
||||
ring: adopt
|
||||
quadrant: languages-and-frameworks
|
||||
|
||||
---
|
||||
|
||||
We now have several years of experiences with Spring Boot,
|
||||
and a big projects Microservice Environment runs completely on Spring Boot,
|
||||
so it's time to update it to "adopt".
|
||||
We now have several years of experiences with Spring Boot, and a big projects Microservice Environment runs completely on Spring Boot, so it's time to update it to "adopt".
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: "Storybook"
|
||||
ring: assess
|
||||
quadrant: tools
|
||||
|
||||
---
|
||||
|
||||
[Storybook](https://storybook.js.org/) is a user interface development environment and playground for UI components. The tool enables developers to create components independently and showcase components interactively in an isolated development environment.
|
||||
Storybook runs outside the main app so users can develop UI components in isolation without worrying about app specific dependencies and requirements.
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: "STRIDE Threat Modeling"
|
||||
ring: trial
|
||||
quadrant: methods-and-patterns
|
||||
|
||||
---
|
||||
|
||||
STRIDE is a model of threat groups that helps to identify security threats to any application, component or infrastructure.
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: "Temporal Modeling"
|
||||
ring: assess
|
||||
quadrant: methods-and-patterns
|
||||
|
||||
---
|
||||
|
||||
Temporal Modeling is way of modeling software systems and components by putting events first.
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
title: "Terraform"
|
||||
ring: adopt
|
||||
quadrant: platforms-and-aoe-services
|
||||
|
||||
---
|
||||
|
||||
[Terraform](https://www.terraform.io/) is a tool for building, changing and versioning infrastructure using the infrastructure as code pattern.
|
||||
Terraform supports popular service providers like AWS, Google Cloud Platform, Azure and many more.
|
||||
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: "Vault"
|
||||
ring: trial
|
||||
quadrant: tools
|
||||
|
||||
---
|
||||
|
||||
[Hashicorp Vault](https://www.vaultproject.io/) is a Go application with a Rest/Cli interface that you can use to securely access secrets.
|
||||
|
||||
@@ -2,6 +2,6 @@
|
||||
title: "Vuex"
|
||||
ring: assess
|
||||
quadrant: languages-and-frameworks
|
||||
|
||||
---
|
||||
|
||||
[Vuex](https://vuex.vuejs.org/) is a state management pattern + library for Vue.js applications.
|
||||
Reference in New Issue
Block a user