Event-Based Programming: Taking Events to the Limit

I have been programming event/message based systems for 25 years and never found a good book on this technique/methodology like this one. Ted does a great job at laying the foundation with a bit of theory (but not maths! So don't be afraid!) and then diving into practice. The text is clear, the diagrams are really good. He also reviews the different types of diagrams: UML state machine, sequence, activity, communication, component wiring diagrams as well as lollipop, SDL, catalysis and espresso diagrams. I was really interested in the chapter on Signal Wiring diagrams, even with my hardware engineering background I didn't know of their use in software engineering. He then quickly reviews a few patterns related to the subject and then dedicates a full chapter on functional roles in a more practical down to the code approach. He finishes the book with 3 case studies that will help understanding the ins and outs of event based programming. Although the example code is supplied in two Microsoft languages (C# and VB Visual Basic) and being a Java person myself, the code is easy to understand and helps a lot. I highly recommend this book and hope that a lot of developers will take on "Event-Based Programming". I do thank the author for the tremendous effort to put together such a good book, with a good balance between theory and practice. In one word: "Bravo!"

This is the second book I have read from this author and as before I found the book very helpful. The book deals with designing applications more the way electrical engineers have been working all along, design each component as independent as possible(decoupled) and at the end hook them up in a way that it gives you the output you want. The book will be specially very helpful to the developers who desing and develop enterprise applications.

This book describes a new way of software system architecture to minimize coupling and increase testability; from the smallest to the largest systems. In an EB system, each part can be developed almost like a separate project, with events hooking everything together at runtime.