This chapter demonstrated how to engineer with ServiceMix, hence we can consider EJB component services equivalent to normal web services so the same rules can be applied from a consumer perspective. This will have greater impact in today's solution infrastructure. This is because in the last one decade or so, we saw the rise of EJB component-based programming. Setting aside (if) any drawbacks, EJB gave us a lot of support for cross cutting concerns like transaction management and instance pooling. For the same reason, lots of solution artifacts are still available and remaining hosted in the form of EJB services. Using an ESB, we are no longer forced to throw away all those investments, instead leverage them in a services ecosystem environment. I am sure I will have an easy time convincing my CTO that I don't need to scrap all my EJB investments, instead I can reuse them in the best possible manner. I hope you will also enjoy the same.