OK Gang! One of our big announcements this 2H SOA Launch is Process Integrity. End to end process integration is required to hold your services, information and users together. This integration must be robust and scalable – otherwise it will restrict you from growing your SOA and building on your initial successes. As you move from basic to advanced SOA, you should be able to use the same products and architectures in an expanded and more advanced way.
So the architecture must start with the ability to provide Process Integrity, even if you don’t use all the capabilities in every project. Robust capabilities must be part of the middleware layer. For example, let’s look at the Enterprise Service Bus. There are several types of ESBs, depending on what they are being used for. An in fact, it’s very possible that you might have different ESBs running in different domains. But whatever ESBs you are running, they must be able to grow with you and provide scalable connectivity as your SOA becomes more advanced. This also means that you might federate multiple ESBs, so that various ESBs are integrated into a larger architecture.
Security and quality of service are key to a successful SOA environment. Even if you don’t need the full set of capabilities in your first couple of projects, you need to ensure that your SOA environment is capable of growing with you. As SOA matures, it will very likely be the basis of a large percentage of IT projects in the future. It’s hard to think of large IT projects that don’t focus on security, scalability, availability and performance. Don’t think of your initial project as something that will be thrown away in the future. Think of them as laying the groundwork for your long-term architecture.
Want to know more about this one?
Watch the process integrity video now.