modri GeekBeardLinks
GeekBeardLinks
/ gist:09e94e9adb609413e53ccba4ad30dcb2
Created
December 16, 2020 13:21
— forked from anonymous/gist:9388472
Summing up contextual influence on systems architecture
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| 1. Monolithic applications and architectures can vary in their monolithness. This is an under-specified description. | |
| 2. Microservice applications and architectures can vary in their microness. This is an under-specified description. | |
| 3. Microservices and monolithic architectures have both benefits and disadvantages. | |
| 4. Organizations will exploit those benefits while working around any weaknesses. | |
| 5. Success of the business is a large influence on the exploitation of benefits and implementation and costs of workarounds. | |
| 6. All benefits and work arounds are context-sensitive. Meaning that they are both technically and socially constructed by the organization that navigates them. | |
| 7. Path dependency is a thing. History matters and manifests in these architectural decisions and evolution in an organization. | |
| 8. Patterns exist to inform practice, not dictate it. Zealous adherence to an architectural pattern brings peril when it is to the exclusion of cultural context in actual practice. | |
| 9. Architectural patterns w |