Managing a

Successful SOA
Deployment for
Your Enterprise

an IT Management eBook
Contents…
Managing a Successful SOA Deployment for Your Enterprise

This content was adapted from Internet.com’s CIO Update Web site. Contributors: Majid Abai,
Mukund Balasubramanian, Theo Beack, Kamran Ozair, and Lionel Carrasco.

2
2 Practical Approaches for Creating an
SOA-Based ­Organization

4 How to Avoid Common SOA Pitfalls

4 6
6 The Nine Requirements for a Successful
SOA Deployment

9 How to Manage SOA Success

9 12

12 Making SOA Sustainable

 Managing a Successful SOA Deployment for Your Enterprise

Practical Approaches for Creating an

SOA-Based Organization
By Majid Abai

B
efore thinking about implementing a service- • How should budgets be allocated for development, mainte-
oriented architecture (SOA), we should consider nance, and future modifications of the services?
an approach to the whole concept in general. • How should requirements from various business units be priori-
I’d like to focus on some practical strategic ap- tized for modification and maintenance of services?
proaches to SOA before and after the implementation. • Whose budget should pay for infrastructure and tools utilized
by all business units?
Consider SOA as a • Should there be a centralized
Design Approach team responsible for quality as-
In his book, Service-Oriented surance of all services (especial-
Architecture: Concepts, Tech- ly performance of the services)
nology, and Design (Prentice or should each project team
Hall), Thomas Erl urges orga- perform this task?

nizations to consider SOA as

a distinct design approach It is important to consider
that, much like object orien- practical answers for the
tation, introduces commonly above questions (and other
accepted principles to govern such questions) prior to the
the positioning, design, and start of development. In order
development of architectural to create consistency, some
components. organizations have created
service development centers,
This is a great idea. In the long also identified as integration
term, you cannot have an or- competency centers; a cen-
ganization that is half SOA and tralized unit supervised by the
half not. The true ROI of SOA enterprise architecture groups
is realized when all redundancies are removed and a true to focus on implementation, maintenance, integration and
shared services organization is created. You either em- cataloging of services.
brace this approach or you do not. There is no half way.
However, other organizations have made business units or
project teams responsible for implementation and mainte-
Consider Budgeting and Responsibilities nance of their respective services and made the enterprise
Prior to the Start of Development architecture team responsible for cataloging and integra-
• Which organization will be responsible for maintenance tion of such services.
of services?

2 Back to Contents Managing a Successful SOA Deployment, an Internet.com IT Management eBook. © 2010, Internet.com, a division of QuinStreet, Inc.
 Managing a Successful SOA Deployment for Your Enterprise
Similarly, and depending on development and mainte-
nance approach chosen, budgeting for such implementa-
tion/maintenance would fall either with the business unit or
through central buckets paid by all business units. In some
organizations, however, the business unit associated with
the development of the service will pay for the develop-
ment, where maintenance is paid by a central budget paid
by all business units.
Consider Top-Down Planning and
Bottom-Up Implementation
Regardless of the project, I have always been an advocate
of starting small, managing problems at a smaller scale,
documenting lessons learned, and then expanding to oth-
er projects. The same is true for an SOA implementation:
While keeping a roadmap at hand and keeping an eye on
the long-term focus of the organization, take a practical
(and strategic) project, and implement it using the SOA
approach.
After implementation, spend some time identifying, docu-
menting, and mitigating problems and risks encountered
during this project, and then scale the approach to two or
more projects.
3 Back to Contents Managing a Successful SOA Deployment, an Internet.com IT Management eBook. © 2010, Internet.com, a division of QuinStreet, Inc.
Consider Creating a Strategy Prior to
Buying the Tools
In many instances, we have seen many projects start by
buying the tool prior to having the requirements docu-
mented. SOA is not an exception. However, this approach
will be counter-productive to an organization’s long-term
plans.
It is important for an organization to create a three- to five-
year strategy for transforming itself into an SOA-based
organization including executive support, business team
alignment, identification of the initial project, practical
steps, governance procedures, scalability schedule, main-
tenance procedures, etc. — prior to identification and pur-
chase of the tools. Identification, evaluation, and purchas-
ing of the tools should be one of the steps in the roadmap
and not the first.
In conclusion, I like to emphasize that considering such fac-
tors while creating a strategy for transforming your organi-
zation to an SOA-based organization will save a lot of mon-
ey and heart-ache for all involved. It will also allow teams
to identify potential pitfalls and create best practices that
could be used throughout the organization through this
important journey.
 Managing a Successful SOA Deployment for Your Enterprise

How to Avoid Common SOA Pitfalls

By Mukund Balasubramanian

I
n a perfect world, the implementation of SOA in your turned a fault. Why was this? Well, WSS4J, in compliance
organization will help better align IT services with with WS-Security, uses “xmldsig” in the name space — but
those day-to-day business processes in which your the .NET service expected “xmlds.” It’s but one example
colleagues, customers, and partners engage. Yet, in of a small inconsistency with big implications.
order to reap the promise of SOA, the prudent CIO must
wrangle both organizational and technology oriented chal- 2. Assuming Standards Are in Place. This is another
lenges — keeping an eye out for common pitfalls. “gotcha.” Not all open source products comply with Web
Services Interoperability (WS-I), though it is the broadly
In our years tackling SOA engagements for clients, we’ve accepted industry standard. This is problematic because
learned a lot about what to watch for. Here are some of the the basic concept of SOA is built atop a foundation of stan-
most common sticking points: dards compliance. Until the day
comes when true adherence is
1. Overlooking Security Incon- the law of the open source land,
sistencies. To assume vendors’ be on the lookout for clashes.
and developers’ security prod-
ucts will work together is to risk Another example: in one of our
the safety and security of the SOA projects, we used IONA’s
corporate data around which you WS-I-compliant Artix Advanced
are building your SOA. SOA Infrastructure Suite as the
SOA backbone to expose a layer
Case in point: in the course of of business services to be con-
a project integrating Apache’s sumed by other applications in-
WSS4J with Infravio’s SOA gov- cluding the open source Sugar-
ernance stack for a large client, CRM/Jira for bug-tracking. Note
we were asked to enable Web that SugarCRM and Jira both
Services Security (WS-Security) expose their Web services using
for a range of services, from en- Remote Procedure Call encod-
cryption to signature verification. ing. All well and good except
WS-Security, as you may know, is broadly accepted among Artix neither supports nor enforces RPC-encoded servic-
open source developers as a security framework, and es. Designing a method to handle RPC-encoded services
WSS4J is a popular implementation of WS-Security. meant we fell six weeks behind.

We successfully enforced security at the intermediary level Pay close attention to the evolution of SOA specifications
until we routed to a secured .NET service. It turns out the by reading trade journals and talking with peers at other
service expected an encrypted message. While we had organizations also working on SOA implementations. Such
the required certificate, every time we hit the service it re- research will tip you off to potential problem areas.

4 Back to Contents Managing a Successful SOA Deployment, an Internet.com IT Management eBook. © 2010, Internet.com, a division of QuinStreet, Inc.
 Managing a Successful SOA Deployment for Your Enterprise
3. Using Poorly Thought Out Naming Conventions.
Here’s another one where thinking ahead can save time
down the road. In an SOA, multiple versions of the same
services are consumed simultaneously by users all over the
organization that may refer to one business process, e.g.,
one “service” using different terms. That’s why it’s critical
that you decide early on how you will include the following
parameters in the name-space of a service and propagate
your chosen naming conventions across the development
team handling your project:
• the business domain the service belongs to
• the service name that explains the business function
• the major version of the service.
4. Relying on Sub-Par Data. Many of the failures we’ve
observed in SOA enablement projects originate from poor
quality data. Careful cleansing of data sources would al-
leviate many of these issues and ensure information is ac-
curate and standardized (one example, “New York,” not
“NYC,” “ny,” “New York City,” etc.).
5. Cutting Corners on Planning. In SOA, as in other kinds
of complex technological projects, the devil is in the de-
tails. As CIO, you need to:
5 Back to Contents Managing a Successful SOA Deployment, an Internet.com IT Management eBook. © 2010, Internet.com, a division of QuinStreet, Inc.
• talk with stakeholders
• cull business users’ wishes for the finished solution
• give all departments a chance to weigh in — they know bet-
ter than anyone how day-to-day processes really work, what
problems need solving, and what business services are most
essential
• translate between the two sides. You or someone you tap
may need to translate business requirements into “developer-
speak” your team can understand. Expect to serve as referee
as business and IT strive to get the project done right
• enforce application testing. Test early and often to make sure
that line of business folks’ wish lists are being translated into
workable code
• set realistic deadlines for integration with partners’ applica-
tions. Insist that everyone on your team adheres to them.
6. Rushing to Deployment. The best SOA projects go live
after a period of months — not when the proverbial switch
is flipped. Start within one department so you can keep
tabs on service granularity (which we guarantee will change
over time) and flush out risk along the way. Enterprise-wide
SOA enablement doesn’t happen overnight, but the ben-
efits it engenders will generate many positive effects for
your organization, from IT to business stakeholders to cus-
tomers and partners.
 Managing a Successful SOA Deployment for Your Enterprise

The Nine Requirements for a

Successful SOA Deployment
By Kamran Ozair

S
OA is an architectural approach that should be a more incremental approach and define services as a by-
looked upon as a journey within an enterprise. product of the different applications they build. When an
Different enterprises embark on the SOA journey enterprise embarks on the SOA journey, there may be many
with different aims. However, the general goals non-believers among the business and IT landscape.
consistently include creating agility, enabling faster time
to market, and encouraging reuse within the enterprise. The initial sets of services also require extra cost and ef-
None of these are easy to achieve and require a set of fort. Hence, it becomes extremely important that the first
guidelines that we will explore implementation involving SOA
in this article. is chosen with care — one that
has a high chance of success
Depending on which article and will help create the mo-
you read or which analyst re- mentum and visibility for the
port you believe, the time for SOA journey.
developing projects using
SOA has arrived. Many enter- 2. Business Agility
prises are already in the pilot One of the key mantras behind
phases of SOA projects while an SOA-based methodology is
others have actually moved that it enables business agility.
implementations into produc- One of the key ingredients of
tion and have services that are how such agility is achieved is
being consumed across the by preparing a business archi-
enterprise. tecture and enabling different
business processes via service
Either way, what I’ve outlined implementations. The tighter
here are the nine essential el- the alignment between the
ements of a successful SOA business architecture and ser-
deployment: vice map, the easier it would
be to keep the two in synch. It will also ensure there is a
1. Careful Choices platform available to absorb the ever-changing business
Different enterprises embark on the SOA journey in dif- requirements and needs, enabling the wider goal of busi-
ferent ways. Some take a holistic view of their business ness agility.
processes and define a service map, whereas others take

6 Back to Contents Managing a Successful SOA Deployment, an Internet.com IT Management eBook. © 2010, Internet.com, a division of QuinStreet, Inc.
 Managing a Successful SOA Deployment for Your Enterprise
3. More Than a Registry
Reuse is the Holy Grail for an SOA-enabled environment.
Most software vendors will talk about their registry prod-
ucts and how one can achieve reuse by ensuring all the
services are visible to the enterprise via a registry. That
may be a good practice but it is not sufficient. In order
to achieve reuse, each service will have to be designed,
implemented, tested, and deployed in a manner that
takes a wider view of the requirements than the particular
project(s) it may be initially implemented for. There also
have to be mechanisms for incorporating newer require-
ments into services and, at the same time, maintaining
backward compatibility.
4. Developers Are People Too
Many developers like to build things from scratch and
sometimes they don’t trust things developed by others. In
addition, many feel that it is easier to build something from
the ground up rather than spend time understanding an
existing service and its usage scenarios.
There has to be a “carrot and stick” approach in order for
developers to line up behind an organizational commit-
ment toward SOA and reuse. There needs to be some ex-
plicit incentive for teams in order for them to reuse existing
services. The initial developers of a service as well as initial
teams that try to reuse them will go through some pain.
They need to be aptly compensated for their extra effort.
Similarly, any team that shies away from using an existing
service should have a lot of explaining to do.
5. Governance
Whether it is defining the design principles behind ser-
vices, a security strategy for services, reuse incentives, or
a clear ownership structure for services, governance has
to be thought through from the initial implementation of
services within the enterprise.
A governance model for SOA should define guidelines
at the architecture level, initiative level, and operational
level. It encompasses best practices and policies and re-
7 Back to Contents Managing a Successful SOA Deployment, an Internet.com IT Management eBook. © 2010, Internet.com, a division of QuinStreet, Inc.
views mechanisms, tools, and methodologies as well as
the organizational structures need to enforce the different
mechanisms.
6. Managing a Shared Infrastructure
As part of implementing multiple applications in an SOA
paradigm, co-deployment of applications on a shared in-
frastructure is a common theme. The applications tend
to use a common set of services and are most likely to
be built on the same architecture. Application boundar-
ies also become blurred in SOA because one project uses
services provided by another.
In such an environment, it is imperative that strong controls
and policies are in place. Aspects like deployment of new
services, configuration management, versioning, mainte-
nance and upkeep, and batch and update cycles have to
be thought through with a shared environment in mind.
Infrastructure and policies have to be designed so they are
able to satisfy the most stringent requirements across the
different applications.
7. Holistic Security
A cohesive security policy and approach has to be thought
through from the onset. Many enterprises have existing
security repositories they want to leverage in an SOA envi-
ronment. On the other hand, many of the products that are
typically deployed in an SOA environment come with their
own security enablement.
A holistic SOA security approach will answer questions
like:
• What will be the approach for authentication?
• What kinds of security standards will be leveraged?
• How will existing security assets get integrated?
• What approach will be taken for message-level security?
• How will fine grain authorization get implemented keeping a
shared application environment in mind?
 Managing a Successful SOA Deployment for Your Enterprise
8. Performance
Application performance is usually calibrated by the needs
of its distinct user community. However, when a service
is being implemented its future usage scenarios may not
be visible. Needless to say that service’s performance
becomes a very important factor in ensuring it is used
across a wider set of applications. Each service needs to
meet the most stringent performance requirement across
applications.
9. Metrics
Success for an SOA initiative needs to be measured and
tied to broader business goals. Questions like the follow-
ing need to be answered before any level of success can
be claimed:
• How much reuse actually happened due to SOA?
• Was there a reduction in time to market for certain
business priorities?
8 Back to Contents Managing a Successful SOA Deployment, an Internet.com IT Management eBook. © 2010, Internet.com, a division of QuinStreet, Inc.
• How reliable was the overall SOA environment?
• Were the SLAs that were defined for the services
properly met?
• Have the performance and scalability requirements
been met?
Some of these questions may be answered via spread-
sheets, but many will require the proper deployment of
tools and processes to provide reliable answers. The suc-
cess of the SOA journey should be quantifiable via metrics
rather than left to perceptions formed due to incomplete
information.
While some of the above guidelines may be applicable for
any software development lifecycle, an SOA environment
imposes a new outlook given the reuse and agility guide-
line requirements.
 Managing a Successful SOA Deployment for Your Enterprise

How to Manage SOA Success

By Theo Beack

I
magine you recently completed the first successful to ensure that every message is guaranteed to be deliv-
phase of your Enterprise SOA Master Plan. Services ered to the right application … What could potentially be
are distributed throughout the enterprise, linking leg- amiss in this picture?
acy applications with your ERP and CRM applications
and are presented to your business users via a new portal To illustrate let me pose a few questions:
interface.
• How many services are currently deployed within
The users love the ease with which they can access all this the organization?
information and conduct their daily tasks. Now that they • Of these services, how many are currently up and running and
know what is possible, they want more, and you are ready how many are experiencing problems?
to give them what they want. • How well does every service
After all, you have just prov- perform its given task? Are
en that SOA is more than a your end-users waiting lon-
mere buzzword. ger to achieve a given task?

• How stable are these ser-

However, no one has yet vices? How are some of these
told you there is a problem. newly created business pro-
cesses and applications af-
This initial, highly success- fected when a crucial service
ful project has introduced a (or services) malfunctions?
new level of complexity into • Can you conduct an impact
your IT organization. Mono- analysis to measure the po-
lithic and heterogeneous tential impact of changes to
applications running in iso- an existing service or set of
lation for many years have services?
suddenly become crucial
components in a more com- By using the principles of
plex organism held together SOA you have been able to
by the principles of SOA. solve a complex problem
and by doing so introduced
The IT architects have very additional complexity into
detailed architectural dia- your IT infrastructure. The
grams to describe it all, the developers wrote thousands of challenge that you now have to face is how to manage
lines of code to make it all work, and the integration team that complexity.
has configured a complex Web of message infrastructure

9 Back to Contents Managing a Successful SOA Deployment, an Internet.com IT Management eBook. © 2010, Internet.com, a division of QuinStreet, Inc.
 Managing a Successful SOA Deployment for Your Enterprise
Approach
SOA Governance is a discipline that, in an ideal world,
should be established early on in the SOA lifecycle. It is
never too late to implement good policies, procedures,
and technology to assist with the management of the
freshly implemented SOA project.
Consider governance a best practice whereby one trans-
forms lessons learned into sound policies, guidelines, and
procedures with the aim of establishing a mature SOA
ecosystem.
Here are five guidelines I consider essential to good
governance:
1. Establish an SOA Competency Center. This is a cross-
functional team of key people that represent different dis-
ciplines within IT. By establishing such a group you facili-
tate communication between the various groups, ensuring
that everyone is represented and that every aspect of the
SOA gets proper consideration.
Furthermore this group can be instrumental in establish-
ing organizational standards, setting guidelines, and cre-
ating blueprints. This core group can also disseminate
knowledge to new groups that need to adopt the SOA
approach.
2. Experience is a good teacher. Blueprints and best
practices can be very good teaching mechanisms. They
are a tangible way in which everyone involved in the SOA
implementation can benefit from the work that has been
done before.
Too many times development teams have to “reinvent the
wheel” in order to solve a particular problem. Identify and
document those solutions that work well and turn them
into patterns that can be used repeatedly.
By making a particular approach repeatable you are able
to reduce risk, shorten development time, and also de-
crease the cost associated with the overall project. Like-
wise, it may be just as important to document those ap-
10 Back to Contents Managing a Successful SOA Deployment, an Internet.com IT Management eBook. © 2010, Internet.com, a division of QuinStreet, Inc.
proaches that don’t work well or which may have failed. By
documenting these so-called anti-patterns one is able to
prevent mistakes from being repeated.
3. Use an SOA Repository. Services are by definition re-
usable and self-describing, but don’t be deceived by this
oversimplified view.
If services are not properly documented and made acces-
sible in a consistent manner, they could become just as
unusable as some of those legacy applications.
Accomplishing such simple tasks as establishing the exact
nature of a service, obtaining the latest service descrip-
tion, or determining the owner of a particular service may
become quite a daunting task if services management in-
frastructure is not put into place. This is where an SOA re-
pository can play an important role. It can become the fo-
cal point where all services can be documented, searched,
and accessed.
4. Monitor Quality of Service (QoS). Bring predictability
to your SOA by implementing service management facili-
ties. What you need is the capability to maintain end-to-
end visibility into your services infrastructure via the ability
to define SLAs (service level agreements), measure services
operation and response levels, analyze service usage and
resource utilization patterns, and proactively be alerted of
potential and imminent service failures.
Stability is the hallmark of a mature system and through
the effective management of your deployed services (and
related infrastructure) you can bring a great measure of
stability to your SOA.
5. Manage the SOA Lifecycle. Create a disciplined and
well-managed SOA lifecycle. In all other areas of IT this
kind of discipline is well established and maintained. SOA
should be no different.
Implement tools and procedures that will help manage
the services development, testing, quality control, deploy-
ment and maintenance processes.
 Managing a Successful SOA Deployment for Your Enterprise

As part of the lifecycle create a services approval process, Acknowledging the complex nature of SOA and taking the
ensuring that services are tested for standards compliance appropriate steps to manage this complexity is a crucial
and services are put through a comprehensive vulnerabil- step toward the successful development, implementation
ity, interoperability, and regression testing process. Imple- and maintenance of an SOA. My advice is to plan for SOA
menting these measures will assist in elevating the overall success. Plan to be hugely successful and in preparation
maturity and robustness of your SOA implementation. consider how you will govern the next generation of busi-
ness applications.
Implementing an SOA entails more than just implementing
a few services or using an ESB (enterprise service bus). SOA
may start out simple, but it inherently introduces complex-
ity into the IT organization. This is mainly due to the nature
of the problems that we are attempting to solve.

11 Back to Contents Managing a Successful SOA Deployment, an Internet.com IT Management eBook. © 2010, Internet.com, a division of QuinStreet, Inc.
 Managing a Successful SOA Deployment for Your Enterprise

Making SOA Sustainable

By Lionel Carrasco

T
he rampant use of web services, and the conse- Sustainable SOA
quent adoption of SOA, makes keeping up with The idea of sustainability isn’t really a new concept but it’s
the rapid changes in technology all the more vital in the process of strategic IT thinking. What it means
critical because these technologies are funda- is that it’s not enough to think about technology in the
mental to the success of a business. context of solving a problem or addressing a need that
you have today. To deliver sustainable value from IT you
SOA’s appeal isn’t difficult to understand. While there is no have to think about how technology will continue to ad-
widely agreed upon definition other than its literal transla- dress your needs going forward.
tion, SOA is an architecture that
relies on service orientation as its Understood this way, SOA is only
fundamental design principle. In viable in the long term when you
an SOA environment indepen- consider the whole lifecycle of
dent services can be accessed services over time as they are
without knowledge of their under- created, changed, and even re-
lying platform implementation. tired. And that’s where sustain-
ability comes in. If you’re not
Adopting SOA is becoming es- thinking ahead to how you will
sential to delivering the business deliver that consistent experi-
agility and IT flexibility required ence you’re not thinking in a sus-
by today’s enterprises. SOA de- tainable way. But the question of
livers a major competitive ad- sustainable SOA is moot without
vantage by increasing organiza- proper governance.
tional agility, allowing companies
to easily assemble and modify
SOA Governance
business processes in response
Companies embarking on the
to market requirements. It also
path to SOA start with a frame-
offers greater flexibility in the
work to guide them through decision-making, accurate
way computer systems can be used to support the busi-
tracking, improved serviceability, and better communica-
ness while lowering implementation costs by increasing
tion. This path is called SOA governance.
reusability.
Essentially, SOA governance is the mechanism to ensure
With SOA, IT assets are aligned to business services in
that the decision making structure is solid, evolution of
a standard, open, and flexible architected fashion. The
business process and technology is encompassed, rela-
promise and goal of SOA is that it can transform the IT as-
tionships between services and parties are managed, and
sets of a business, making it possible to do more with less,
that there is compliance with the laws, policies, standards,
and faster while keeping pace with technology changes.
and procedures under which an organization operates.

12 Back to Contents Managing a Successful SOA Deployment, an Internet.com IT Management eBook. © 2010, Internet.com, a division of QuinStreet, Inc.
 Managing a Successful SOA Deployment for Your Enterprise
SOA governance is an extension of IT governance that
focuses on the lifecycle of services and composite appli-
cations in an organization’s service-oriented architecture.
Because SOA applications are intrinsically fragmented,
they introduce new governance challenges. But with the
proper business semantics, policies, principles, standards,
procedures, and processes in place, businesses can realize
the full benefit of service orientation.
An effective SOA governance platform not only helps busi-
ness and IT teams better identify which projects contribute
most to business goals, but it also empowers employees
to work and collaborate more efficiently by clearly defining
their roles and responsibilities.
Without SOA governance, SOA has little chance of be-
coming sustainable. In a study on SOA and governance,
industry analyst firm Gartner concluded that the most
common reason for failure in SOA projects encompass-
ing 50 services or more was a lack of working governance
mechanisms.
The bottom line is that any enterprise that fails to realize
the importance of an effective governance and sustain-
able structure may not stand to benefit much from an
SOA transition.
13 Back to Contents Managing a Successful SOA Deployment, an Internet.com IT Management eBook. © 2010, Internet.com, a division of QuinStreet, Inc.
Sustainable Strategies
Your SOA approach should align processes governance
and information technology with business objectives.
You should view your organization as a system, and see
its technology, information, and processes as components
of an overall structure. You should consider that only the
proper articulation and alignment of processes and busi-
ness objectives will make an SOA implementation sustain-
able, manageable, and profitable.
The key to success in implementing a sustainable and func-
tional SOA takes into account four main components:
• Design a framework that integrates throughout the lifecycle
of SOA. This includes people, processes, and technology do-
mains, all around the goals of supporting business processes.
• A ssess the IT maturity stage, business goals, and technical con-
text constraints of the enterprise.
• Create a plan that covers the design, construction, deploy-
ment, and operation of artifacts, principles, policies, etc., to
help IT adopt and evolve an SOA.
• Produce a sound adoption roadmap encompassing the “To-
day” and the “To Be” scenarios.
By using a systemic approach you get a clear advantage
to working independently of the different legacy software
systems you might have, as well as optimize the solution
and ensure sustainable profitability. The result will be sus-
tainable SOA.