- http://markburgess.org/blog_cap.html
- http://www.haskellforall.com/2019/06/
- https://jessitron.com/2016/05/07/tradeoffs-in-coordination-among-teams/
-
https://codahale.com/you-cant-sacrifice-partition-tolerance/#fn:4
- Whether a system favors yield or harvest (or is even capable of reducing harvest) tends to be an outcome of its design.
- https://medium.com/@kentbeck_7670/test-commit-revert-870bbd756864
- https://trunkbaseddevelopment.com/styles/
- DevOps Topologies
Effective Organizational Cultures that make the “what” and the “how” more explicit, such as Unicorn Project: 5 Ideals or Phoenix Project: 3 Ways, are ones that prioritize Consistency or Availability.
They offer more advice on ways to improve the process as part of an emphasis on Continuous Learning as a means of Focus, Flow, Joy, rather than for the sake of facilitating Joy at Work.
todo:
- Relating whether a system optimizes for harvest or yield to software engineering.
-
Relating CAP tradeoffs to software cultures:
- google: consistency over availability
- amazon: availability over consistency
- If a company tolerates divergence, consistency and availability can be maintained even with partition failures.
- Most companies do not tolerate divergence, which often manifests itself in not granting their employees sufficient autonomy to succeed.