Q3 updates and new (empty articles)
This commit is contained in:
Bernhard Behrendt
@@ -1,6 +0,0 @@
|
||||
---
|
||||
title: "ADR"
|
||||
ring: assess
|
||||
quadrant: pattern
|
||||
|
||||
---
|
||||
@@ -1,6 +0,0 @@
|
||||
---
|
||||
title: "Alpakka"
|
||||
ring: assess
|
||||
quadrant: languages-and-frameworks
|
||||
|
||||
---
|
||||
@@ -1,6 +0,0 @@
|
||||
---
|
||||
title: "Application and business metrics"
|
||||
ring: TBD
|
||||
quadrant: pattern
|
||||
|
||||
---
|
||||
@@ -1,6 +0,0 @@
|
||||
---
|
||||
title: "Automatic linting"
|
||||
ring: trial
|
||||
quadrant: pattern
|
||||
|
||||
---
|
||||
@@ -1,6 +0,0 @@
|
||||
---
|
||||
title: "Blameless post mortems"
|
||||
ring: TBD
|
||||
quadrant: pattern
|
||||
|
||||
---
|
||||
@@ -1,6 +0,0 @@
|
||||
---
|
||||
title: "Consumer Based Contract"
|
||||
ring: TBD
|
||||
quadrant: pattern
|
||||
|
||||
---
|
||||
@@ -1,6 +0,0 @@
|
||||
---
|
||||
title: "CRC"
|
||||
ring: assess
|
||||
quadrant: pattern
|
||||
|
||||
---
|
||||
@@ -3,7 +3,4 @@ title: "Elasticsearch"
|
||||
ring: trial
|
||||
quadrant: platforms-and-aoe-services
|
||||
|
||||
---
|
||||
Elasticsearch is a REST-based search and analytics engine based on Lucene. Unlike its competitor Apache Solr, it was developed in the beginning with clustering and scaling in mind. It allows you to create complex queries while still delivering results very fast.
|
||||
|
||||
At AOE, we use Elasticsearch for logging as well as our own search solution [Searchperience](http://www.searchperience.com/). We recently moved the Searchperience stack from Solr to Elasticsearch and think this was the right decision. Especially in terms of scaling, ease of use and performance, Elasticsearch really shines. Also, the API design took some of the learnings from Apache SOLR into account - for example, the queryDSL is a powerful way of describing different search use cases with highly flexible support of aggregations, etc.
|
||||
---
|
||||
@@ -1,6 +0,0 @@
|
||||
---
|
||||
title: "Google container engine"
|
||||
ring: trial
|
||||
quadrant: platforms-and-aoe-services
|
||||
|
||||
---
|
||||
@@ -1,4 +0,0 @@
|
||||
---
|
||||
title: "Grafana"
|
||||
ring: assess
|
||||
quadrant: platforms-and-aoe-services
|
||||
@@ -1,6 +0,0 @@
|
||||
---
|
||||
title: "GraphQL"
|
||||
ring: assess
|
||||
quadrant: TBD
|
||||
|
||||
---
|
||||
@@ -1,4 +0,0 @@
|
||||
---
|
||||
title: "GRPC"
|
||||
ring: assess
|
||||
quadrant: TBD
|
||||
@@ -1,6 +0,0 @@
|
||||
---
|
||||
title: "Helm- Terraform"
|
||||
ring: trial
|
||||
quadrant: TBD
|
||||
|
||||
---
|
||||
@@ -1,6 +0,0 @@
|
||||
---
|
||||
title: "Invision"
|
||||
ring: trial
|
||||
quadrant: tools
|
||||
|
||||
---
|
||||
@@ -1,18 +1,6 @@
|
||||
---
|
||||
title: "Jest "
|
||||
ring: assess
|
||||
title: "Jest"
|
||||
ring: trial
|
||||
quadrant: tools
|
||||
|
||||
---
|
||||
[Jest](https://facebook.github.io/jest/) is a javascript testing framework by facebook to test javascript code **and** react applications / components.
|
||||
|
||||
We started using Jest (and [watchmen](https://github.com/facebook/watchman)) instead of Karma because it:
|
||||
|
||||
- gives us integrated mocking library
|
||||
- gives us integrated support for testing "promises"
|
||||
- gives us integrated code coverage report
|
||||
- automatically runs tests related to changed files (instead of all tests)
|
||||
- gives us parallel test execution
|
||||
- gives us snapshot testing for react components
|
||||
|
||||
It is easy to set up. And even if you have a running setup with karma/chai you can easily replace karma with jest. With a small [workaround](https://medium.com/@RubenOostinga/combining-chai-and-jest-matchers-d12d1ffd0303#.3callo273), chai and jest test matchers work fine together.
|
||||
---
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: "Kubernetes"
|
||||
ring: assess
|
||||
ring: trial
|
||||
quadrant: platforms-and-aoe-services
|
||||
|
||||
---
|
||||
|
||||
@@ -1,6 +0,0 @@
|
||||
---
|
||||
title: "MKDOCS"
|
||||
ring: asses
|
||||
quadrant: tools
|
||||
|
||||
---
|
||||
@@ -1,6 +0,0 @@
|
||||
---
|
||||
title: "Google container engine"
|
||||
ring: trial
|
||||
quadrant: pattern
|
||||
|
||||
---
|
||||
@@ -1,6 +0,0 @@
|
||||
---
|
||||
title: "PACT"
|
||||
ring: assess
|
||||
quadrant: tools
|
||||
|
||||
---
|
||||
@@ -1,6 +0,0 @@
|
||||
---
|
||||
title: "Port and Adapters"
|
||||
ring: trial
|
||||
quadrant: TBD
|
||||
|
||||
---
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: "Pipeline as Code"
|
||||
ring: assess
|
||||
ring: adopt
|
||||
quadrant: methods-and-patterns
|
||||
|
||||
---
|
||||
|
||||
6
radar/2017-03-01/port-adapters.md
Normal file
6
radar/2017-03-01/port-adapters.md
Normal file
@@ -0,0 +1,6 @@
|
||||
---
|
||||
title: "Port and Adapters"
|
||||
ring: assess
|
||||
quadrant: methods-and-patterns
|
||||
|
||||
---
|
||||
@@ -3,20 +3,4 @@ title: "Puppet Environments"
|
||||
ring: assess
|
||||
quadrant: platforms-and-aoe-services
|
||||
|
||||
---
|
||||
|
||||
Puppet
|
||||
------
|
||||
|
||||
Puppet is an Open Source configuration management tool. It is used by a wide range of different companies world-wide, e.g. the Wikimedia Foundation, Mozilla, Reddit, CERN, Dell, Rackspace, Twitter, the New York Stock Exchange, PayPal, Disney, Citrix Systems, Spotify, Oracle, the University of California Los Angeles, the University of North Texas, QVC, Intel, Google and others.
|
||||
|
||||
Puppet has been the basic tool to address Continuous Configuration Automation (CCA) in AOE's [Infrastructure as Code](/methods-and-patterns/infrastructure-as-code.html) strategy (IaC) for more than 4 years.
|
||||
|
||||
Puppet Environments
|
||||
-------------------
|
||||
|
||||
Intended to give projects the means to develop and maintain their own infrastructure, separated and not influenced by other projects, Puppet environments, together with Puppet module versioning and ENC, have been introduced.\
|
||||
Puppet Environments are rated "Trial". It supports our strategy of Infrastructure as Code (IaC) and links it to our DevOps approach, enabling project teams to set up and customize their own infrastructure.
|
||||
|
||||
Teams that want to use the Puppet Environments service from the AOE IT Team will find detailed information about the implemented CI/CD process for this.
|
||||
|
||||
---
|
||||
@@ -1,4 +0,0 @@
|
||||
---
|
||||
title: "Security awareness training"
|
||||
ring: assess
|
||||
quadrant: TBD
|
||||
@@ -1,6 +0,0 @@
|
||||
---
|
||||
title: "Self service infrastructure"
|
||||
ring: assess
|
||||
quadrant: pattern
|
||||
|
||||
---
|
||||
@@ -1,6 +0,0 @@
|
||||
---
|
||||
title: "Spark"
|
||||
ring: asses
|
||||
quadrant: languages-and-frameworks
|
||||
|
||||
---
|
||||
@@ -1,6 +0,0 @@
|
||||
---
|
||||
title: "Swift"
|
||||
ring: trial
|
||||
quadrant: languages-and-frameworks
|
||||
|
||||
---
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: "Vue.js"
|
||||
ring: assess
|
||||
ring: trial
|
||||
quadrant: languages-and-frameworks
|
||||
|
||||
---
|
||||
|
||||
@@ -3,13 +3,4 @@ title: "Wiremock"
|
||||
ring: trial
|
||||
quadrant: tools
|
||||
|
||||
---
|
||||
**[WireMock](http://wiremock.org/docs/)** is an HTTP mock server - it can be used to mock APIs for testing.
|
||||
|
||||
At its core, it is a web server that can be prepared to serve canned responses to particular requests (stubbing), and that captures incoming requests so that they can be checked later (verification). It also has an assortment of other useful features including record/playback of interactions with other APIs, injection of faults and delays, simulation of stateful behavior.
|
||||
|
||||
It can be used as a library by any JVM application, or run as a standalone process either on the same host as the system under test or a remote server. All of WireMock's features are accessible via its REST (JSON) interface and its Java API. Additionally, the mock server can be configured via JSON files.
|
||||
|
||||
At AOE, we use WireMock as a standalone server to mock APIs that are outside our system context to get a stable environment for testing and rapid feedback. Besides the decoupled test and development advantages, the mocked APIs can also be used in contract-based tests. We also use embedded WireMock in functional tests to stub external services. The explicit test of faults are especially helpful in building and testing the [resilience of your application](/methods-and-patterns/resilience-thinking.html).
|
||||
|
||||
Because of the features such as flexible deployment, powerful request matching and record/payback interactions, as well as the fact that the server runs stable in our project environments, we classify WireMock as *trial*.
|
||||
---
|
||||
Reference in New Issue
Block a user