References
Brandolini, A. (n.d.). Introducing EventStorming. Leanpub.
Brooks, F. P., Jr. (1974). The Mythical Man Month and Other Essays on Software Engi‐ neering. Reading, MA: Addison-Wesley.
Eisenhardt, K., & Sull, D. (2016). Simple Rules: How to Succeed in a Complex World.
London: John Murray.
Esposito, D., & Saltarello, A. (2008). Architecting Applications for the Enterprise: Microsoft® .NET. Redmond, WA: Microsoft Press.
Evans, E. (2003). Domain-Driven Design: Tackling Complexity in the Heart of Soft‐ ware. Boston: Addison-Wesley.
Feathers, M. C. (2005). Working Effectively with Legacy Code. Upper Saddle River, NJ: Prentice Hall PTR.
Fowler, M. (2002). Patterns of Enterprise Application Architecture. Boston: Addison- Wesley.
Fowler, M. (2019). Refactoring: Improving the Design of Existing Code (2nd ed.). Bos‐ ton: Addison-Wesley.
Fowler, M. (n.d.). What do you mean by “Event-Driven”? Retrieved August 12, 2021, from https://martinfowler.com/articles/201701-event-driven.html.
Gamma, E., Helm, R., & Johnson, R. (1994). Design Patterns: Elements of Reusable Object-Oriented Software. Reading, MA: Addison-Wesley.
Gigerenzer, G., Todd, P. M., & ABC Research Group (Research Group, Max Planck Institute, Germany). (1999). Simple Heuristics That Make Us Smart. New York: Oxford University Press.
Goldratt, E. M. (2005). Beyond the Goal: Theory of Constraints. New York: Gildan Audio.
Goldratt, E. M., & Goldratt-Ashlag, E. (2018). The Choice. Great Barrington, MA: North River Press Publishing Corporation.
Goldratt-Ashlag, E. (2010). “The Layers of Resistance—The Buy-In Process Accord‐ ing to TOC.” (Chapter 20 of the Theory of Constraints handbook.) Bedford, Eng‐ land: Goldratt Marketing Group.
![]() |
Garcia-Molina, H., & Salem K. (1987). Sagas. Princeton, NJ: Department of Com‐ puter Science, Princeton University.
Helland, P. (2020). Data on the outside versus data on the inside. Communications of the ACM, 63(11), 111–118.
Hohpe, G., & Woolf, B. (2003). Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions. Boston: Addison-Wesley.
Khononov, V. (2022). Balancing Coupling in Software Design. Boston: Addison- Wesley.
Khononov, V. (2019). What Is Domain-Driven Design? Boston: O’Reilly.
Martraire, C. (2019). Living Documentation: Continuous Knowledge Sharing by Design.
Boston: Addison-Wesley.
Millett, S., & Tune, N. (2015). Patterns, Principles, and Practices of Domain-Driven Design (1st ed.). Nashville: John Wiley & Sons.
Myers, G. J. (1978). Composite/Structured Design. New York: Van Nostrand Reinhold. Ousterhout, J. (2018). A Philosophy of Software Design. Palo Alto, CA: Yaknyam Press.
Richardson, C. (2019). Microservice Patterns: With Examples in Java. New York: Man‐ ning Publications.
Vernon, V. (2013). Implementing Domain-Driven Design. Boston: Addison-Wesley. Vernon, V. (2016). Domain-Driven Design Distilled. Boston: Addison-Wesley.
West, G. (2018). Scale: The Universal Laws of Life and Death in Organisms, Cities and Companies. Oxford, England: Weidenfeld & Nicolson.
Wright, D., & Meadows, D. H. (2009). Thinking in Systems: A Primer. London: Earthscan.