Both Udi and Eric are competent and experienced architects in designing SOAs . On the technology side, Udi ("The software simplest") specializes in .NET development; e.g., his nServiceBus framework is a very good example of an endpoint-ware ServiceBus (vs. middleware ServiceBuses which is what most ESBs do). For his part, Eric is a Java and C++ expert and author of Java Messaging (one of the best books on JMS and web services ) and has also has lots of experience in financial systems. Together, the three of us bring a lot of real-life experience of building large and complicated system into this project.
The current game plan is for Eric to focus on the SOA pitfalls ("anti-patterns") part of the book, Udi to provide a "putting-it-all-together" chapter , and for me to cover what’s left. I am sure however, that their experience and insight will also help make the other parts of the book (even? ) better.
InformationWeek Tech Digest, Nov. 10, 2014Just 30% of respondents to our new survey say their companies are very or extremely effective at identifying critical data and analyzing it to make decisions, down from 42% in 2013. What gives?