[{"_1":2,"_42":-5,"_43":-5},"loaderData",{"_3":4,"_10":11,"_40":-5,"_41":-5},"root",{"_5":-5,"_6":-5,"_7":-5,"_8":9},"user","shoppingCartId","toast","locale","en","routes/_store+/_readers+/email_author.$slug/route",{"_12":13,"_39":-5},"book",{"_14":15,"_16":17,"_18":19,"_20":21,"_22":23,"_24":25},"id","Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6Qm9va1Byb2R1Y3QvMzYxNDM","title","Event Sourcing in Python","state","published","contactAuthorMethod","email","aboutText","

This book presents a coherent pattern language for event sourced applications and reliable distributed systems.

The main chapters of the book are organised in three parts. Part 1 describes how to make an event sourced domain model. Part 2 describes how to make an event sourced application. Part 3 describes how to make a reliable distributed system from a set of event sourced applications. Each part of the book has five chapters. Each chapter has complete working examples written in the Python programming language. The examples in later chapters build on the examples in previous chapters.

This book can be used as a general guide for event sourcing, event-driven systems, and the tactical patterns of Domain-Driven Design. It is an accompaniment to the popular Python eventsourcing library, and gives an overview of the design of this library. The chapter examples present a distilled and enhanced version of the code available in the Python eventsourcing library.

The book's prologue shows how Christopher Alexander's pattern language scheme was originally intended as a scheme for describing events, and is best understood as an application of the event-oriented modern process philosophy of Alfred North Whitehead. A discussion of the way pattern language was taken up in software development reveals how the event-oriented nature of Alexander's scheme was overlooked. The prevailing general understanding of things that has predominated objected-oriented analysis and design is identified as the two-hierarchies scheme, which involves the substance-quality categories that Whitehead had already shown to be inadequate. The deficiency of the two-hierarchies scheme is explained, and the detrimental consequences for software design patterns, object-oriented programming, software architecture, and the agile approach to software development are highlighted. A return to the event-oriented approach that is exhibited in Whitehead's and Alexander's schemes is proposed under the name of event-oriented analysis and design. A detailed summary of Whitehead's scheme is provided as a second introductory chapter at the start of the book.

The book's epilogue gives an overview of both the event-oriented moment-by-moment, person-centred, psychology of Carl Rogers and its application as the collaborative or nonviolent communication scheme of Marshall Rosenberg.

This book is primarily aimed at professional software developers working under deadlines to create reliable maintainable software applications and systems that support non-trivial business processes in both startups and established corporations, especially Python developers.

This book is suitable for anybody interested in the history and philosophy of technology. It will also be interesting and useful for students and teachers of computer science and software engineering.

","authors",[26],{"_14":27,"_28":29,"_5":30},"Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6UHJvZHVjdEF1dGhvci8zNzgwOA","name","John Bywater",{"_31":32},"avatar",{"_33":34,"_35":36,"_37":38},"url","https://d308did4coypzi.cloudfront.net/avatars/1442274/medium/JohnBywater_Suit_Oxford.jpeg?1603919366","styleName","medium","exists",true,"currentUser","routes/_store+/_layout","routes/_store+/_readers+/_layout","actionData","errors"]

Email the author