BPEL provides an enterprise and cross-enterprise approach for SOA with simple descriptions of how to orchestrate processes and invoke external programs, applications, and/or services. In practice, BPEL is actually extending the existing WSDL standards. WSDL is an XML-based language for describing web services that includes the details of how to consume them.

BPEL does not replace Java, .NET, or any other programming language, rather it complements them. In this chapter, we will talk about interoperability between BPEL and Java. BPEL provides excellent workflow process capabilities; however, one may find competing arguments from associates that it may not be worth it due to investments required in learning and using BPEL, additional infrastructure requirements, and an additional layer for troubleshooting. BPEL won't solve all the enterprise applications' problems, rather it is a tool to simplify reusability of discrete systems and facilitate seamless process agility to design and deploy enterprise class composite applications. The key to success is to realize when and how to use BPEL in implementing composite applications.