Jul 13, 2015

The Benefits of Implementing a Service Oriented Architecture as Part of Mobile Rollout

If you are in the process of rolling out systems into new channels (e.g. a mobile presence), migrating toward a cloud-based deployment or integrating with a new partner, you should give consideration to how your systems are integrated. An effective integration infrastructure facilitates business agility, simplifies on premise and in-cloud integration and reduces operating costs.

Traditionally, when organisations developed web-based systems (internal and customer facing) the major elements of the system (application, database, etc) tended to be tightly coupled and integrated. This has led to downstream challenges when organisations have been tasked with delivering new channels such as a mobile presence. In these cases, they have faced the challenge of how to integrate the application for the new channel with the legacy applications. In many cases they choose to tightly integrate the applications. In choosing this integration approach, organisations miss an opportunity to lay a foundation for future business\IT agility and reduced operating cost.

An alternative approach\solution to the above challenge would be to implement a Service Oriented Architecture (SOA) architecture within the environment. In a SOA-based environment, existing applications are made available as discreet, system-independent services. These services may be called by other service enabled applications, inside or outside your organisation (e.g. integrate your Oracle ERP system with a partners/customers SAP system ).

Having a SOA-based infrastructure and service-enabled systems in place enables the organisation to react positively to a number of common business scenarios:

  • Mobile Application Provisioning – May be achieved by integrating the new application with the services that have already been provisioned in the service layer.
  • Application Integration – May be readily achieved by integration at the service level or at the business process level (using Business Process Management (BPM)).
  • New Business Process Definition – May be defined and implemented in BPM.
  • On-Premise\In-cloud Integration – May be achieved in the service layer or BPM.
  • Integration with new Partners – May be achieved in the service layer or via BPM.


The above scenarios detail how the implementation of a service oriented architecture provides a platform which enables the organisation to react to ever more common business scenarios in an agile, controlled and cost effective manner. It should be noted that the rollout of SOA is not necessarily an all or nothing rollout – The rollout can (and from a risk mitigation perspective should) be undertaken on a project-by-project, incremental basis where the return on investment increases as the number of service-provisioned applications increases).

If you would like further details on any of the topics discussed above, please email John Rushe or call on +353 91 745567.


Other News Articles