Taking Care – Error Handling - Applied SOA Patterns on the Oracle Platform - page 538

Summary
We would like to remind you about the statement we made at the beginning of Chapter 3 ,
Building the Core - Enterprise Business Flows . Yes, OSB (the ESB SOA composite pat-
tern from Oracle) is probably the only pattern you need in your SOA infrastructure. Maybe
your business does not need long running asynchronous processes; it also could be that
your security requirements are soft, and two core security policies implemented in OSB by
default will suffice. A number of service artifacts can be insignificant, and you can survive
without Central Repository; however, if your business applications do not need proper ex-
ception handling, please check the pulse of your business—maybe it's already dead!
Whatever framework is described in Chapter 1 , SOA Ecosystem - Interconnected Prin-
ciples, Patterns, and Frameworks , will be responsible for your core business operations;
exception handling will be an essential part of it. If you, as an enterprise SOA architect
(and we assume that you are), are involved in the resolution of critical situations around
apps that are delivered by your team, then carefully designed logging and EH will save you
from a lot of trouble (and not only technical). Make it proactive and preventive using the
patterns and rules explained in this chapter and most of these situations will be avoided.
This chapter concludes the CTU architectural and technical example started in Chapter 3 ,
Building the Core - Enterprise Business Flows . In the next and last chapter, we will discuss
the most complex SOA patterns and their realizations in support of the distribution and
analysis of events, parallel in-memory processing, and the readiness of Oracle Cloud.