Loosely-Coupled Architecture - how to get rid of the domino effect
I finished work on my presentation about “Loosely-Coupled Architecture - how to get rid of the domino effect” which will be shown as in Wrocław .NET User Group.
If you are interested in this topic you can check my training offer.
You can find slides from my presentation on OneDrive.
Traditionally, while creating our system, you don’t focus on creating our components separated from each other. As a result, one problem can lead you to the domino effect - the whole system stops working. How to counteract it?
“Loosely coupled architecture” is recognized as the main factor to create a highly-scalable system. It allows you to make changes in your application which won’t effect on their other part. See yourself what are the criteria of this architecture to be able to introduce it to your solution from the very beginning.
- Nicole Forsgren, Jez Humble, Gene Kim - Accelerate: The Science of Lean Software and DevOps
- Simon Brown - Modular Monolith
- Cohesion & Coupling
- Martin Fowler - Presentation Domain Data Layering
- Jimmy Bogard - Vertical Slice Architecture
- David Parnas - On the Criteria To Be Used in Decomposing Systems into Modules
- Sandi Metz -All the Little Things
- Adam Brett - DRY (Don’t Repeat Yourself) is a Fallacy
- Tef Books - Write code that is easy to delete, not easy to extend
- Eric Evans - Domain Driven Design
- Nick Tune -Tech Strategy Blog
- Alberto Brandolini - Event Storming
- Alberto Brandolini - Strategic Domain Driven Design with Context Mapping
- Greg Young - The art of destroying software