Feedback by Mahbouba Gharbi 20.04.2022 #23
Replies: 3 comments 1 reply
-
As the curstor for FLEX, here are my 2cts on this. Upfront Disclaimer:
[1] https://github.com/isaqb-org/curriculum-flex/blob/main/docs/02-modularization/02-learning-goals.adoc |
Beta Was this translation helpful? Give feedback.
-
@aheusingfeld Would we like to continue the discussion? |
Beta Was this translation helpful? Give feedback.
-
I would certainly upvote the ideas of “when not to use microservices” and also for “monolith to microservices” (without the going back, actually). Why “when not to use microservices”? Why “monolith to microservices”? |
Beta Was this translation helpful? Give feedback.
-
In German language:
Translation:
The current version of the curriculum is from Nov 2015. that's almost 7 years old.
Within these years topics around flexible architectures changed. New aspects were added, some have been detailed and recommendations have been created: Best practices and Do's and Dont's.
Explicitly other architects like "Richardson et al" recommend to force monolithic systems again: "From Monoliths to Microservices and back again".
Especially the learnings and recommendations of microservice approaches are applied back onto the design of monolithic systems.
Another topic which is only indirectly mentioned in the Curriculum, is the aspect of loss of control in complex (Microservice-)Systems. How can we avoid these and how do all aspects (Monitoring, CI/CD, etc.) finally play together?
Beta Was this translation helpful? Give feedback.
All reactions