diff --git a/LICENSE.txt b/LICENSE.txt index 12b597d..9c0e840 100644 --- a/LICENSE.txt +++ b/LICENSE.txt @@ -1,3 +1,5 @@ +The license applies to the generator code and not the articles in the "radar" folder. (Read also the README.md in this folder) + Apache License Version 2.0, January 2004 diff --git a/README.md b/README.md index d28ac7e..9b208b9 100644 --- a/README.md +++ b/README.md @@ -2,6 +2,14 @@ A static site generator for AOE Technology Radar +## Usage for your own radar? +The generator is free to use under Open Source License - in fact there are already some other Radars published based on our Radar and there are also Contributions back. + +However please be aware: +* The text and descriptions for the articles in the "radar" are copyright protected by AOE and they are not allowed to use in your radar +* It would be nice to mention in radar that the generator is based on this repository. +* Also when you want to reuse the CSS and Styling: Change the font (it is a licensed font) and the colors (It using AOE CI) + ## Installation ``` diff --git a/assets/images/microservices-pyramid.png b/assets/images/microservices-pyramid.png new file mode 100644 index 0000000..4cf9691 Binary files /dev/null and b/assets/images/microservices-pyramid.png differ diff --git a/js/components/QuadrantSection.js b/js/components/QuadrantSection.js index 79a4520..606052c 100644 --- a/js/components/QuadrantSection.js +++ b/js/components/QuadrantSection.js @@ -61,8 +61,7 @@ export default function QuadrantSection({ quadrantName, groups, big = false }) { {!big && (
- Quadrant - Overview + Zoom in
)} diff --git a/radar/2018-03-01/microservices.md b/radar/2018-03-01/microservices.md index 8b6a999..1ee5c27 100644 --- a/radar/2018-03-01/microservices.md +++ b/radar/2018-03-01/microservices.md @@ -5,7 +5,12 @@ quadrant: methods-and-patterns --- -We continue to stand by are belief in the microservices concept. However, it's worth mentioning that we we had to learn some lessons when it came to resilient thinking and deployment-related dependencies between microservices. +We continue to belief in the microservices concept and its related patterns and best practices. However, it's worth mentioning that we we had to learn some lessons when it came to resilient thinking and deployment-related dependencies between microservices. We feel that our microservice-based applications are more robust than monolithic ones have been. Thanks to the split of the overall complexity into multiple services, new employees or team members are becoming productive within days or a few weeks. + +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) +