diff --git a/package.json b/package.json index 6446108..ac54a22 100644 --- a/package.json +++ b/package.json @@ -11,7 +11,7 @@ "build:static": "aoe_technology_radar-createStaticFiles" }, "dependencies": { - "aoe_technology_radar": "https://github.com/aoepeople/aoe_technology_radar.git" + "aoe_technology_radar": "../aoe_technology_radar" }, "engines": { "node": "~15.9" diff --git a/public/favicon.ico b/public/favicon.ico new file mode 100644 index 0000000..ac826e4 Binary files /dev/null and b/public/favicon.ico differ diff --git a/public/images/microservices-pyramid.png b/public/images/microservices-pyramid.png new file mode 100644 index 0000000..3503f7f Binary files /dev/null and b/public/images/microservices-pyramid.png differ diff --git a/public/images/strategic-domain-driven-design-relationships.png b/public/images/strategic-domain-driven-design-relationships.png new file mode 100644 index 0000000..8a280ca Binary files /dev/null and b/public/images/strategic-domain-driven-design-relationships.png differ diff --git a/public/logo.svg b/public/logo.svg new file mode 100644 index 0000000..b71405b --- /dev/null +++ b/public/logo.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/public/robots.txt b/public/robots.txt new file mode 100644 index 0000000..e9e57dc --- /dev/null +++ b/public/robots.txt @@ -0,0 +1,3 @@ +# https://www.robotstxt.org/robotstxt.html +User-agent: * +Disallow: diff --git a/radar/2017-03-01/rabbitmq.md b/radar/2017-03-01/rabbitmq.md index adc85b2..5528c1d 100644 --- a/radar/2017-03-01/rabbitmq.md +++ b/radar/2017-03-01/rabbitmq.md @@ -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) diff --git a/radar/2017-03-01/strategic-domain-driven-design.md b/radar/2017-03-01/strategic-domain-driven-design.md index 5868d2b..047a82a 100644 --- a/radar/2017-03-01/strategic-domain-driven-design.md +++ b/radar/2017-03-01/strategic-domain-driven-design.md @@ -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. \ No newline at end of file diff --git a/radar/2018-03-01/microservices.md b/radar/2018-03-01/microservices.md index 1ee5c27..5645450 100644 --- a/radar/2018-03-01/microservices.md +++ b/radar/2018-03-01/microservices.md @@ -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) diff --git a/src/index.tsx b/src/index.tsx deleted file mode 100644 index 3f47daa..0000000 --- a/src/index.tsx +++ /dev/null @@ -1,13 +0,0 @@ -import React from 'react'; -import ReactDOM from 'react-dom'; -import App from 'aoe_technology_radar/src/components/App'; -import 'aoe_technology_radar/src/index.scss'; -import {Item} from "aoe_technology_radar/src/model"; -import radardata from './rd.json'; - -ReactDOM.render( - - - , - document.getElementById('root') -);