Database Reference
In-Depth Information
recourses from standard authorities for SAML, OAuth, and so on. This section is just a
technical recap of the absolute bare minimum requirements to link previous paragraphs
dedicated to SOA principles with the soon-to-arrive SOA design rules based on patterns
applied in particular SOA frameworks.
As an experienced architect, you are certainly quite familiar with all the technologies we
will briefly touch on now.
XML
This is the foundation of most of the standards and applications, not only SOA. Please
note that you do
not
have to use XML to make your platform service-oriented in order to
achieve goals of service-orientation, but you will find it rather difficult not to do so. You
will have to replace quite a sizeable amount of movable and static elements of your infra-
structure (configuration files, interchange messages, transformation mappings, contracts,
and so on) with some similar but older formats such as CSV, EDIFACT, and X12 with lots
of unexpected consequences. Modern standards such as JSON are also not entirely XML-
free. So, we would like to suggest something for your own architectural benefits. Please
look at the simple W3C School XML quiz (
http://www.w3schools.com/xml/
xml_quiz.asp
)
; it will only take five minutes. If your score is less than 100 percent, we
suggest you refresh yourself by reading a good XML topic.
Web Services (WS)
If service is an atomic building block of the whole SOA, then web services are the most
popular variant of these building blocks. The reason for this is in an object/XML serial-
izer, which is the native part of any WS and the link between a detached WSDL-based
service contract and core service logic. For the Oracle platform (but not only), quite natur-
ally employed Java marshaling/unmarshaling, Java-WS (or JWS) technology would be
based on one of the following serialization APIs:
• Java architecture for XML binding: JAXB (exists on multiple implementations
but is not always fully compatible).
• A more advanced JiBX. This can inject the conversion code directly into Java
classes during the post-compilation process, and by doing so, improve the per-
formance considerably when compared to JAXB. Also, it has its own runtime-
binding component.
• Simplified mapping-free version of marshaler: XStream.
JAXB is still the most popular one because of the number of characteristics it offers:
Search WWH ::
Custom Search