AJR/TechradarDev
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge pull request #30 from AOEpeople/newBuilderVersion

Browse Source 
Use new version of aoe_technology_radar (with create react app)
This commit is contained in:
bmsuseluda
2021-06-17 13:57:24 +02:00
committed by GitHub
parent 6ef4b30c31 8e5b2438cf
commit 85d8da4345
14 changed files with 5425 additions and 4460 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
radar/2017-03-01/rabbitmq.md
View File

@@ -11,5 +11,3 @@ There are several alternative solutions to RabbitMQ, e. g. the free Apache Activ
We use RabbitMQ internally for transferring messages safely in our logging ecosystem between [Logstash](/platforms-and-aoe-services/elk-stack.html) proxies and servers using direct and fan-out exchanges for delivering messages to appropriate destinations. RabbitMQ is also used to asynchronously trigger Jenkins jobs from our SCMs to mitigate heavy load on the SCMs, usually caused by Jenkins polls for SCM changes. Additionally, some critical events for monitoring are using RabbitMQ for guaranteed notification.
RabbitMQ is rated "Trial". It fits into our approach to build robust, [resilient systems](/methods-and-patterns/resilience-thinking.html) and use [asyncronous messages](/methods-and-patterns/decoupling-infrastructure-via-messaging.html) for loosely coupled communications between components. In practice, RabbitMQ proved to be stable and dealt well with service interruptions from failures and maintenance slots. A common pain point is RabbitMQ as a single point of failure disrupting the data flow in a system. This issue is currently approached by setting up a HA cluster for RabbitMQ. The outcome of this approach will clarify the extent of future usage of RabbitMQ in our systems.
![](/assets/images/rabbitmq.png)

2
radar/2017-03-01/strategic-domain-driven-design.md
View File

@@ -13,7 +13,7 @@ It is a pattern familiy focused on using and defining Bounded Context and thinki
A context map and a common conceptional core help to understand and improve the overall strategic picture. Especially with the [Microservice](/methods-and-patterns/microservices.html) approach, it is important to define and connect services following the low coupling - high cohesion principles by idendifying fitting bounded contexts.
The following chart gives an overview of possible relationships between bounded contexts:
![strategic-domain-driven-design-relationships](/assets/images/strategic-domain-driven-design-relationships.png)
![strategic-domain-driven-design-relationships](/images/strategic-domain-driven-design-relationships.png)
While we have found that this approach is especially useful in designing distributed systems and applications with [microservices](/methods-and-patterns/microservices.html), we have also extended this approach to provide guidlines for general enterprise architectures.

2
radar/2018-03-01/microservices.md
View File

@@ -12,5 +12,5 @@ split of the overall complexity into multiple services, new employees or team me
In order to get microservices right and to benefit from the advantages, there is a lot more required.
The following "pyramid of need" for microservices shows this:
![microservices pyramid of need](/assets/images/microservices-pyramid.png)
![microservices pyramid of need](/images/microservices-pyramid.png)