{"id":543,"date":"2015-02-20T11:51:00","date_gmt":"2015-02-20T11:51:00","guid":{"rendered":"http:\/\/www.jameshatton.co.uk\/blog\/?p=543"},"modified":"2019-12-30T04:27:46","modified_gmt":"2019-12-30T04:27:46","slug":"evaluating-the-adoption-of-a-soa-approach-to-developing-applications","status":"publish","type":"post","link":"https:\/\/www.jameshatton.co.uk\/blog\/2015\/02\/20\/evaluating-the-adoption-of-a-soa-approach-to-developing-applications\/","title":{"rendered":"Evaluating the adoption of a SOA approach to developing applications"},"content":{"rendered":"\n

At the current \u2018evolutionary stage\u2019 of E-Business technologies, the multi-tier architecture (illustrated in Figure 1) utilised by Picture Rights can be regarded as a more traditional design. <\/p>\n\n\n\n

\"\"
Figure 1 – Example of multi-tier architecture <\/figcaption><\/figure>\n\n\n\n

As a common business approach, this multi-tier architecture is relatively mature and stable with the advantage of being well-supported. When based on standards, this architecture allows for future developments because each tier can be readily exchanged due to defined interfaces between tiers.<\/p>\n\n\n\n

This model automates many activities of the business processes, for example, a client could submit a web form with a picture attachment to request a quote. However, the model fundamentally relies on the human operator as input to the process so the level of automation is \u2018capped\u2019 e.g. the user may have to re-submit multiple forms.<\/p>\n\n\n\n

The Service Oriented Architecture (SOA) is an alternative approach whereby the most relevant group of technologies is the Web Services Architecture (WSA). The primary goal of adopting a WSA approach is to enable automation by providing interfaces between the company\u2019s electronic business systems and external or internal software applications. Figure 2 outlines the operation of web services.<\/p>\n\n\n\n

\"\"
Figure 2 Web service operation outline<\/figcaption><\/figure>\n\n\n\n

The WSA does not replace the existing architecture but is complementary: the web service still uses a web server component of multi-tier architecture. A web service is provided and third-party software clients can easily connect by discovering these services listed in a service directory in a process governed overall by standardised protocols.<\/p>\n\n\n\n

Web Services for the Company<\/h2>\n\n\n\n

Each web service should mirror a specific function because a host of web services can be listed in a UDDI registry and a third-party can access any specific services required. The table below provides examples of web services that Picture Rights could publish.<\/p>\n\n\n\n

Web Service<\/strong><\/td>Function\/Procedure<\/strong><\/td>Audience<\/strong><\/td><\/tr>
Novelty<\/td>1. Client searches catalogue of novelty image backgrounds.
2. Client selects an image and submits photo.
3. Combined photo\/background image returned with quote reference and price. <\/td>		High street shops
Online novelty print websites<\/td><\/tr>
Order<\/td>1. Client submits quote reference and makes payment in system.
2. Order details returned (e.g. address) and instructions for shipment to Picture Rights (if applicable) <\/td>		Any party using other web services.<\/td><\/tr>
Portfolio<\/td>1. Client requests portfolio
2. Before\/After restoration image catalogue returned <\/td>		Picture Rights\u2019 own website
Reseller of image restoration service<\/td><\/tr>
Repair<\/td>1. Client submit(s) images to be repaired with description of work required.
2. Quote reference and due date returned. <\/td>		Picture Rights\u2019 own website
Reseller of image restoration service<\/td><\/tr>
Progress<\/td>1. Client requests status of progress
2. Service returns status e.g. work started, complete, dispatched <\/td>		Any third party system (e.g. high street) or own website.<\/td><\/tr>
Enquiry<\/td>1. Client sends general enquiry e.g. can you do this
2. Text response is returned by customer service agent <\/td>		Any third party system e.g. specialist reseller or own website<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The web services could interface with the existing, potentially legacy, business systems via an \u201cadapter\u201d so that for example, once an order is placed, the photo requiring repair is placed in a folder on the graphic technician\u2019s PC with an accompanying brief. The processes resulting from WSA adoption is more efficient (compared to, for example, email exchange) so enables the business to meet deadlines better while saving costs (through increased productivity).<\/p>\n\n\n\n

APIs can be published by the company for third-parties to benefit from using these web services in their applications. Resellers, for example, could seamlessly integrate the novelty picture service into a website where a consumer interacts with the web store and is not aware of Picture Rights\u2019 involvement.<\/p>\n\n\n\n

This well-defined and seamless integration would be appealing for prospective partners to widen the market for Picture Rights through more partners. Additionally WSA would strengthen the existing relationships with current partner and \u2018lock\u2019 the partner into this process (cost of change from using Picture Rights as a service provider would be higher).<\/p>\n\n\n\n

The adoption of WSA could also mean that Picture Rights\u2019 own applications could access the web services of other organisations. For example, a web services client could fetch the image of a third-party catalogue (verifying licensing and cost) and order this as part of Picture Rights\u2019 own novelty service, when a client order is placed (via a partner).<\/p>\n\n\n\n

Although the SOA is a conceptually better approach compared to alternative architectures, it has commercial benefits whereby it is predominantly adopted by business to gain competitive advantage. To maintain that competitive advantage, a business must then continue to evolve its SOA to embrace the latest developments. SOA is however still, arguably, in its infancy because a variety of standards exist (few being de jure) and standards\/technologies are continuously emerging to supersede others. Additionally some of the proprietary products or technologies associated with the standards are not well documented.<\/p>\n\n\n\n

Tools and Standards<\/h2>\n\n\n\n

Web services are designed to automate processes by interoperability, which itself is achieved by adherence to standards. A number of standards are available in the web services protocol stack as described below.<\/p>\n\n\n\n

Level<\/strong><\/td>Technology<\/strong><\/td>Standards and Resources<\/strong><\/td><\/tr>
Directory<\/td>UDDI<\/td>UDDI Version 3.0.2 (OASIS, 2004)<\/td><\/tr>
Service Description<\/td>WSDL<\/td>Web Services Description Language (WSDL) 1.1 (W3C, 2011)<\/td><\/tr>
Message Encoding<\/td>SOAP, XML, XML-RPC, REST<\/td>SOAP Version 1.2 Part 1: Messaging Framework (Second Edition) (W3C, 2007)<\/td><\/tr>
Network Transport<\/td>HTTP, SMTP, FTP<\/td>W3C, IETF<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Some standards compete and\/or are complementary such as SOAP and REST. It is arguable that the adoption of standards (as opposed to technology implementation) is crucial to realising the return on investment of a particular technology because some standards will prevail in the long-term over others. The resources in the table above provide a good reference to the standards required so that a brief can be better provided to developers for the prospective web services. Additionally the Web Services Interoperability Organization (WS-I) provides many standards (in the form of profiles) to help ensure web services are interoperable.<\/p>\n\n\n\n

If development was performed \u2018in-house\u2019 (this could be preferable as the adoption of SOA would be core to the business strategy) then financial investment in required technologies could be kept minimal by utilising open source products \u2013 which tend to better implement standards than proprietary systems and functionality can often be extended with plug-ins. The coding of many of these standards could even be done with text editors but the tools below will automate many aspects of the development process.<\/p>\n\n\n\n

Tool<\/strong><\/td>Purpose<\/strong><\/td>Resources<\/strong><\/td><\/tr>
Eclipse IDE<\/td>Framework software for developing software applications.<\/td>https:\/\/eclipse.org<\/td><\/tr>
Axis2<\/td>Web Services \/ SOAP \/ WSDL engine with server\/client components<\/td>http:\/\/axis.apache.org\/axis2\/java\/core\/<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Recommendation<\/h2>\n\n\n\n

Picture Rights has to operate a technical transformational process (e.g. image repair) as well as market its services to consumers or businesses \u2013 and provide customer service. It is difficult for an SME (with 30 personnel) to coordinate all these functional areas effectively. The adoption of a SOA could have a huge transformative effect on the business model. Web services enable a business to transition from the using the Web for business to consumer (B2C) interaction to a transactional approach to using the Web i.e. business to business (B2B) automation. By providing web services to third parties, who will interact with customers themselves (marketing, customer service), Picture Rights could both extend their market reach but also better focus on the core business processes that add value \u2013 the technical manipulation of images.<\/p>\n\n\n\n

With such a dramatic effect on the business, the adoption of web services may appear disruptive but WSA technology could integrate with existing applications and enhance processes (via \u201cadapters\u201d bridging web services to legacy applications). This could separate customer interfaces (e.g. third parties or own website) from operational (transformative) processes. As the, increasing, adoption of web services is standards driven (consisting of a layered technology stack); confidence can be had in the long-term usage of this technology.<\/p>\n\n\n\n

The resources involved could be minimal initially: Many tools (arguably the better products) such as Apache are freely available and the developments\/training involved can produce results early on. The \u201ctrialability\u201d and scalability of the SOA approach means that observable benefits could be realised throughout the adoption cycle: The UDDI structure also means web services could be added over time. Using cloud hosting services reduces the technology dependence (compared to purchasing physical servers) and these could be scaled in-line with demand (e.g. seasonal demand for personalised cards).
Ultimately the WSA approach therefore reduces many of the fixed costs associated with the business processes and better controls the variable costs, reducing risk to the business. WSA is a modern approach and more businesses are adopting Software as a Service (Kontzer, 2012), known as Saas, it is important that Picture Rights capture this market potential.<\/p>\n\n\n\n

References<\/h2>\n\n\n\n

The Open University\n(2014) T320 \u2018Introduction to web services\u2019<\/em>,\nBlock 3 Part 1, \u2018E-business technologies: foundations and practice\u2019, Milton\nKeynes, The Open University<\/p>\n\n\n\n

W3C (2001) \u2018Web Services Description Language (WSDL) 1.1\u2019<\/em> (Online)
http:\/\/www.w3.org\/TR\/wsdl (Accessed 25th February 2015) <\/p>\n\n\n\n

W3C (2007) \u2018SOAP Version 1.2 Part 1: Messaging Framework\n(Second Edition)\u2019<\/em> [online] http:\/\/www.w3.org\/TR\/soap12\/ (Accessed 25th\nFebruary 2015)<\/p>\n\n\n\n

Oasis (2004) \u2018UDDI Version 3.0.2\u2019<\/em> [online] https:\/\/www.oasis-open.org\/committees\/uddi-spec\/doc\/spec\/v3\/uddi-v3.0.2-20041019.htm\n(Accessed 25th February 2015)<\/p>\n\n\n\n

Web Services\nInteroperability Organization \u2018Basic\nProfile Version 1.2\u2019<\/em> [online] http:\/\/ws-i.org\/Profiles\/BasicProfile-1.2-2010-11-09.html\n(Accessed 25th February 2015)<\/p>\n\n\n\n

Kontzer, T (2012) \u2018Strategic Tech Slideshow: Gartner’s Global\nSaaS Spending Report: Plenty of Room for Growth\u2019 <\/em>[online] http:\/\/www.cioinsight.com\/c\/a\/Strategic-Tech\/Gartners-Global-SaaS-Spending-Report-Plenty-of-Room-for-Growth-282322\n(Accessed 26th February 2015)<\/p>\n","protected":false},"excerpt":{"rendered":"

At the current \u2018evolutionary stage\u2019 of E-Business technologies, the multi-tier architecture (illustrated in Figure 1) utilised by Picture Rights can be regarded as a more traditional design. As a common business approach, this multi-tier architecture is relatively mature and stable with the advantage of being well-supported. When based on standards, this architecture allows for future developments because each tier can be readily exchanged due to defined interfaces between tiers. This model automates many activities of the business processes, for example, a client could submit a web form with a picture attachment to request a quote. However, the model fundamentally relies on the human operator as input to the process so the level of automation is \u2018capped\u2019 e.g. the user may have to re-submit multiple forms. The Service Oriented Architecture (SOA) is an alternative approach whereby the most relevant group of technologies is the Web Services Architecture (WSA). The primary goal of adopting a WSA approach is to enable automation by providing interfaces between the company\u2019s electronic business systems and external or internal software applications. Figure 2 outlines the operation of web services. The WSA does not replace the existing architecture but is complementary: the web service still uses a web[…]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"ngg_post_thumbnail":0,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[20],"tags":[32],"class_list":["post-543","post","type-post","status-publish","format-standard","hentry","category-stem","tag-essay"],"featured_image_src":null,"author_info":{"display_name":"james","author_link":"https:\/\/www.jameshatton.co.uk\/blog\/author\/james\/"},"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p89zH1-8L","jetpack-related-posts":[],"jetpack_likes_enabled":true,"_links":{"self":[{"href":"https:\/\/www.jameshatton.co.uk\/blog\/wp-json\/wp\/v2\/posts\/543","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.jameshatton.co.uk\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.jameshatton.co.uk\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.jameshatton.co.uk\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.jameshatton.co.uk\/blog\/wp-json\/wp\/v2\/comments?post=543"}],"version-history":[{"count":2,"href":"https:\/\/www.jameshatton.co.uk\/blog\/wp-json\/wp\/v2\/posts\/543\/revisions"}],"predecessor-version":[{"id":548,"href":"https:\/\/www.jameshatton.co.uk\/blog\/wp-json\/wp\/v2\/posts\/543\/revisions\/548"}],"wp:attachment":[{"href":"https:\/\/www.jameshatton.co.uk\/blog\/wp-json\/wp\/v2\/media?parent=543"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.jameshatton.co.uk\/blog\/wp-json\/wp\/v2\/categories?post=543"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.jameshatton.co.uk\/blog\/wp-json\/wp\/v2\/tags?post=543"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}