Fix typos and change some grammatical constructions
This commit is contained in:
daniel.motzko
@@ -4,6 +4,10 @@ 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.
|
||||
[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.
|
||||
|
||||
Concourse claims to be "simple" but has a steep learning curve in the beginning till it gets simple to use.
|
||||
Concourse is used in the Congstar Team to automate infrastructure deployments.
|
||||
@@ -12,5 +12,4 @@ Amazon EKS is used as part of the infrastructure in the Congstar project.
|
||||
Different Amazon EKS Clusters are in use on a variety of environments like development, integration, testing and production.
|
||||
We experienced that Kubernetes version updates are done without major efforts or impact to the running cluster.
|
||||
|
||||
Amazon EKS is fully supported by Terraform which brings the advantage that its configuration is written in code,
|
||||
which fulfils the infrastructure as code philosophy.
|
||||
Amazon EKS is fully supported by Terraform which brings the advantage that its configuration is written in code, which fulfils the infrastructure as code philosophy.
|
||||
@@ -17,9 +17,7 @@ It's like brainstorming - with the goal to visualize a business line or process.
|
||||
|
||||
Event Storming is done in a workshop format.
|
||||
|
||||
To get a business process modeled quickly and complete, it's important to get domain experts, developers, UX and
|
||||
everybody else who is involved to some extent in the related business line into one room.
|
||||
With virtually unlimited space for modeling using big paper rolls put onto the walls, equipped with colored stickies
|
||||
and markers, the modeling workshop can start.
|
||||
To get a business process modeled quickly and complete, it's important to get domain experts, developers, UX and everybody else who is involved to some extent in the related business line into one room.
|
||||
With virtually unlimited space for modeling using big paper rolls put onto the walls, equipped with colored stickies and markers, the modeling workshop can start.
|
||||
|
||||
During the workshop, the goal is to model the big picture, without limiting or focusing just on parts of a process.
|
||||
|
||||
@@ -4,7 +4,8 @@ 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.
|
||||
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.
|
||||
|
||||
GraphQL was developed by Facebook around 2010 and releases 2015.
|
||||
The main challenge it solves is to improve communication between browser and server on high dynamic web apps.
|
||||
|
||||
@@ -4,7 +4,10 @@ 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.
|
||||
[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.
|
||||
|
||||
Jaeger is a great tool for troubleshooting distributed systems, such as microservice architectures. Developers and Operation can quickly see communication between services, and what data is communicated where.
|
||||
Errors in services can be traced to the originating system. Global trace identifiers are communicated using B3 headers. Jaeger supports Zipkin, which allows easy migration von OpenZipkin & co.
|
||||
Jaeger is a great tool for troubleshooting distributed systems, such as microservice architectures.
|
||||
Developers and Operation can quickly see communication between services, and what data is communicated where.
|
||||
Errors in services can be traced to the originating system.
|
||||
Global trace identifiers are communicated using B3 headers. Jaeger supports Zipkin, which allows easy migration von OpenZipkin & co.
|
||||
|
||||
@@ -4,8 +4,9 @@ ring: trial
|
||||
quadrant: methods-and-patterns
|
||||
---
|
||||
|
||||
When deciding on a system architecture we are always striving for technology neutralism. This is to allow us to stay
|
||||
flexible with future decisions. Micro Frontends can be a tool to support us with this goal.
|
||||
When deciding on a system architecture we are always striving for technology neutralism.
|
||||
This is to allow us to stay flexible with future decisions.
|
||||
Micro Frontends can be a tool to support us with this goal.
|
||||
We favor protocols and methods, such as plain HTML and HTTP, over specific technologies when designing Micro Frontends.
|
||||
|
||||
Since Micro Frontends have proven to allow use move fast and agile, we moved this pattern to "trial".
|
||||
@@ -4,7 +4,8 @@ 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.
|
||||
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.
|
||||
|
||||
OpenAPI v2 version is basically the former Swagger - and Swagger provides useful tools for OpenAPI like the online editor and viewer http://editor.swagger.io/
|
||||
We have also found that this version currently have a good tool support across languages, so you will find API client and server generation tools for a lot of languages, which makes it quite easy to connect to an API that is described in OpenAPI standard.
|
||||
|
||||
@@ -6,4 +6,3 @@ featured: false
|
||||
---
|
||||
|
||||
[PostgreSQL](https://www.postgresql.org/) is a powerful, open source object-relational database system with over 30 years of active development that has earned it a strong reputation for reliability, feature robustness, and performance.
|
||||
|
||||
|
||||
@@ -4,11 +4,8 @@ ring: adopt
|
||||
quadrant: methods-and-patterns
|
||||
---
|
||||
|
||||
The reactive style of programming promotes event-based thinking and modeling --
|
||||
and by that assists in creating more decoupled solutions.
|
||||
The reactive style of programming promotes event-based thinking and modeling - and by that assists in creating more decoupled solutions.
|
||||
|
||||
Synergies arise, when people understand the concepts of this pattern: by using marble diagrams,
|
||||
which are a de-facto standard in visualizing algorithms in a reactive style, a common ground for communication
|
||||
is available regardless of the programming language used.
|
||||
Synergies arise, when people understand the concepts of this pattern: by using marble diagrams, which are a de-facto standard in visualizing algorithms in a reactive style, a common ground for communication is available regardless of the programming language used.
|
||||
|
||||
When appropriate, we choose more explicitly the Reactive Programming pattern and therefore moved this to "adopt".
|
||||
@@ -4,5 +4,7 @@ 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.
|
||||
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.
|
||||
SonarQube is also being used for Static Application Security Testing (SAST) which scans our code for potential security vulnerabilities and is an essential element of our Secure Software Development Lifecycle.
|
||||
@@ -4,5 +4,6 @@ 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](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.
|
||||
|
||||
@@ -8,13 +8,10 @@ Temporal Modeling is way of modeling software systems and components by putting
|
||||
|
||||
The usual way of modeling software is to find structures, things and relations.
|
||||
We try to find the relevant aspects of a domain and put all properties into an object-oriented model.
|
||||
Trying to create a second model for a related business process, having the structural model already in place,
|
||||
might result in a process representation that is tightly coupled with the assumptions built up from the structural
|
||||
model and too far away from reality.
|
||||
Trying to create a second model for a related business process, having the structural model already in place, might result in a process representation that is tightly coupled with the assumptions built up from the structural model and too far away from reality.
|
||||
|
||||
By focusing on the domain processes first, one can visualize all aspects of a process over time.
|
||||
Having the process visualized, allows to see potential pitfalls or forgotten aspects.
|
||||
With a temporal model at hand, it is easy to create an object-oriented or structural model that perfectly
|
||||
represents all required information.
|
||||
With a temporal model at hand, it is easy to create an object-oriented or structural model that perfectly represents all required information.
|
||||
|
||||
We tried this method when tackling big or complex domains.
|
||||
|
||||
@@ -4,4 +4,6 @@ ring: adopt
|
||||
quadrant: languages-and-frameworks
|
||||
---
|
||||
|
||||
As writing frontend applications becomes more complex, [TypeScript](https://www.typescriptlang.org/) allows us to scale client side code easily, even with large code bases. We use typescript successfully at production for many projects and we are only going to use it even more in the future. We highly recommend using typescript over javascript, therefore we have decided to move it to adopt.
|
||||
As writing frontend applications becomes more complex, [TypeScript](https://www.typescriptlang.org/) allows us to scale client side code easily, even with large code bases.
|
||||
We use Typescript successfully at production for many projects and we are only going to use it even more in the future.
|
||||
We highly recommend using Typescript over JavaScript, therefore we have decided to move it to adopt.
|
||||
|
||||
Reference in New Issue
Block a user