Scalability
means different things to different people. It’s like a group of
blindfolded people touching an elephant on different sides. Each person
will have their own explanation and individual experience. Similarly, in
the Oracle SOA Suite world, expansion and scalability of an Oracle SOA
Suite environment means different things for everyone. For
Administrators, it’s about adding more managed and admin servers to the
existing Oracle SOA environment. For SOA Developers, it means adding
more services and BPEL processes in the existing service repository. For
IT Management, it is about how they can expand their initial Oracle SOA
footprint to add more systems, attain further ROI and truly expand to a
service oriented architecture framework for their enterprise.
From
an Oracle SOA Suite middleware perspective, a detailed analysis of your
current environment should be done. Ask yourself some of the following,
when planning for Oracle SOA Suite scalability and expansion:
- How much additional traffic can my current Oracle SOA Suite instance handle?
- How easy is it to add more storage capacity?
- How many more transactions can be processed?
In
this series of 3 blog posts, I will focus on a few different components
from service design, infrastructure setup and management/governance,
which can be used as reference when you are considering scaling out your
Oracle SOA Suite environment. Read the complete article here.
For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.