The Service Oriented Architecture and Its Concepts - Assignment Example

The service oriented architecture (SOA) Introduction: Service Oriented Architecture (SOA) is independent of vendors and technology. These are designsand design patterns, which are used as services. It is piece of software that is working as an application in terms of functionality. For example the retrieval of online bank statement, the submission of online form for opening a novel account, booking of airline and the reservation of tickets, etc. The cooperation among systems connected through the internet is the core and basic functionality of the Service Oriented Architecture (SOA). Basic aim behind this work is to illustrate the service oriented architecture and its related concepts as use of web services, total cost of ownership, advantages and disadvantages of using standards based integration strategy Analyze 5 ways in which SOA reduces the total cost of ownership (TCO) The Service Oriented Architecture (SOA) reduces the total cost of ownership in different ways some of them are: The cost of project implementation is reduced due to the use of Service Oriented Architecture (SOA), this happens through the use of standardized practices tools and methodologies. According to Bluenog (2014) the Service Oriented Architecture (SOA) also becomes the reason to minimize the cost of production and maintenance that is a big deal of the services. In the integration process of architecture, redundancy is eliminated that results into a decrease of cost by the use of Service Oriented Architecture (SOA). The cost is minimized for integration specialist resource on each unit level of the business. The Service Oriented Architecture (SOA) increases the agility that becomes the reason for different kinds of business needs and also makes low the total cost of ownership (TCO). The Service Oriented Architecture (SOA) principles do the task of minimizing the total cost of ownership (TCO). The adoptions of Service Oriented Architecture (SOA) increase the flexibility of growth for the organization as well as the reduction in the cost. The structure and culture of the organization gets change by the application of Service Oriented Architecture (SOA). Some of the factors that considered as the drivers of business include in the following: Innovative opportunities for getting enhancements. Cost saving factors like Total Cost of Ownership (TCO). The higher degree of automation is possible only through the adoption of Service Oriented Architecture (SOA). Real time demand services are possible to deliver on time that also becomes the reason for reducing the cost. The maintenance cost is also minimized within working environment given by Service Oriented Architecture (SOA). Classon and Prem (n.d) stated that the best Information strategy necessarily achieves the business targets. Platform dependency increases the risk and increases the cost. The Total Cost of Ownership (TCO) is possibly reduced for maintenance cost saving techniques resulting from the implementation of Service Oriented Architecture (SOA). Examine 5 ways in which XML enables data and information exchange between clients and servers using Web services in a SOA environment. The defined set of rules and protocols are used within the Service Oriented Architecture (SOA). In the construction of Service Oriented Architecture (SOA) use of XML is performed. The description of services is made through the Web Services Description Language (WSDL) and the Service Oriented Architecture protocols (SOAP) are only defining the communication protocols. The transfer of data between servers and clients relies on some internet technologies such as HTTP and HTTPS. HTTP and HTTPS are protocols that are used for transfer of data between computers on the internet. These protocols allow communication between different services. Data between services is encoded in some format which is known as eXtensible Markup Language (XML). Web services uses XML format to transfer data and information between different computers. Whether these computers are connected in local area network or wide area network, web services can be used in both cases. Text based language is used for exchange of data between client and server the language is called Extensive Markup Language (XML). Bos (2012) pointed that the Extensive Markup Language (XML) provides the ability to structured, validated and transformation of data. The core Extensive Markup Language (XML) and the associated technologies with it give the structured, meaningful and exchangeable transfer of data. From the definition of web services used for definition and gives the description information. Web services provide standard methods for transfer of information. The unique way for communication independent of frameworks, software applications, etc. The format used is close to machine format so the independent environment could create for communication. That format is created through the use of Web Services Description Language (WSDL). The conversation is made through the simple messages form via HTTP. “The concept of service-oriented architecture (SOA) in Oracle E-Business Suite, XML Gateway inbound messages can be service enabled.” Simple Object Access Protocol (SOAP) Guaranteed Delivery SOAP Servlet (Inbound) Authentication, Authorization, and Message extraction. Web Service Security XML Gateway Services Classon and Prem (n.d) in their work discussed that web services mostly work for improvement in different kinds of E-business. The services are given to e-commerce’s that enhances the reliability. Compare and contrast the loosely coupled architecture, to a tightly coupled architecture in terms of TCO, maintenance, and implementation issues. Service Oriented Architecture (SOA) is self contained and its functionality is loosely coupled architecture form. The core principles and disciplines Service Oriented Architecture (SOA) follows are: standardization, loosely coupled, reusable, compostable, automatic, stateless, abstract, and discoverable. The theme for which Service Oriented Architecture (SOA) is called loosely coupled is due to the independence nature. The environment in which Service Oriented Architecture (SOA) operates is independent of platforms that generalize it. The other reasons, which make the Service Oriented Architecture (SOA) as a loosely coupled architecture, are the independent of design and independent of evolution. It contains the feature of decupling from the environment. The possibility of interpretability is also one major feature of Service Oriented Architecture (SOA) (Bos, 2012). The feature of Service Oriented Architecture (SOA) as a loosely coupled architecture makes it unique and opens the ways for exploration without the interference of venders. The architecture grows freely and creates novels methods to capture the new emerging features of volatile nature and demands of information technology. This feature matures the Service Oriented Architecture (SOA). Comparison and contrast in terms of Total Cost of Ownership (TCO) issues: In finding total cost of ownership (TCO) the loosely coupled architecture is best, because loosely coupled architecture modules has no dependency or minor dependency on each other that’s why it is little easy to estimate the cost of any project. If modules are tightly coupled then there are many difficulties and problems for estimating the cost because first there will be a need to analyze that which modules are dependent on each other and which changes will be required based on that dependency and how much time will be required for implementing the dependency. Therefore, total cost of ownership (TCO) will be high in tightly coupled architecture as compared to loosely coupled architecture. When any changes will be needed total cost of ownership will increase in case of tightly coupled architecture. Comparison and contrast in terms of maintenance issues: In a tightly coupled architecture it is very difficult and awful task to maintain software, because all or many modules are dependent on each other. If any change occurs in one module then it impacts on all modules, which are dependent on that module. Programmers need to analyze those modules, which are dependent on this module and this module is dependent on which modules so it is time consuming also. In tightly coupled architecture, it is very painful to maintain the software. According to Slama et al., (2004) in contrast to tightly coupled architecture, loosely coupled architecture is very easy to maintain. Modules has little dependency or no dependency on each other so if any change occurs in one module then it is very easily handled, because that needs changes on specific module or minor changes in a dependent module. Failure in one component will cause to failure in all dependent components. Comparison and contrast in terms of implementation issues: Tightly coupled architecture has many problems in implementation as compared to a loosely coupled architecture. Programmers need to be very careful in case of developing the module in case of tightly coupled architecture, because they need to take care of dependencies and relations of that module with other modules. So it will take more time and more cost rather than implementing loosely coupled architecture. Software testing will take more time in case of tightly coupled architecture. Therefore software testing cost will be also high in a tightly coupled architecture. In case of any change in requirements in one or more modules, it needs implementation on all modules that affect the change, so all the dependent modules will need implementation changes. Changes in many modules due to one change need more implementation cost and time and there are many chances of errors in different modules, which may cause to a project or software failure (Karatoprak, 2012). In case of loosely coupled architecture implementation cost is low as compare to tightly coupled architecture. While implementing the module in loosely coupled architecture programmer doesn’t need to analyze the relationships and dependencies of different modules so the implementation cost will be not much high (Classon and Prem, n.d). In case of change in one module there can be minor changes in its dependent module so cost will be low and minimum time will be required to implement the change. Analyze three advantages and disadvantages of using standards - based integration strategy. Advantages of using standards based integration strategy The best features provided by Service Oriented Architecture (SOA) are based on standards based integration. The benefits are: reduction of cost, agility, advantage of increased competitive, time to deliver product to market takes less time, consolidation, and alignment. The Service Oriented Architecture (SOA) is layer based on a mature model used for integration (Bos, 2012). Financial services provided over the internet capture the advantages provided by Service Oriented Architecture (SOA). The XML based standards are used for achieving the financial services. Global Trade Association (GTA) generated the fpMl as the standard of XML for exchanging of currency, commodities and swaps of equity. In a work PolarLake (n.d) described that these standards were highly useful for the organizations that emerged the technology. Many other finance based organizations like insurance companies, stock exchange, etc. take advantages of using the Service Oriented Architecture (SOA). The standards based integration strategies are simple in implementation and minimize the time to market and also use the available tools in the market. The rule based transformation is the advantage of standards based integration strategies and many powerful performances are also provided by this technology. Multi models support the integration based architecture. These are loosely coupled and standard based techniques that generalize the products and reduce the cost of ownership (TCO) (Karatoprak, 2012). Disadvantages of using standards based integration strategy Along with exhaustive advantages of Service Oriented Architecture (SOA) there are some gaps considered as disadvantage of using standards based integration strategy. The constructions of organization specific frameworks of XML are focused instead of working on business logic. These organization specific frameworks require extra investment that increase the overall cost of the projects within an organization. This leads more investment for increase in cost of development and maintenance. In some cases these developed strategies need to be emend for adjustment of new business changes. That ultimately increases the cost of rework and effect negatively the performance of the financial organization (Slama et al., 2004). The implementation process of the Enterprise Application Integration (EAI) products that is not able to bring flexible solution and some time these products are not XML centric. These products may deliver in long time and decrease the value in the market. The market always needs to capture the new technology in a short time because this is the competitive nature of a product in available and coming in the market. Mostly Enterprise Application Integration (EAI) products go over budget or get failed. The cost and complexity should be minimized to capture the target market. The use of Enterprise Application Integration (EAI) increases the Total Cost of Ownership (TCO) (PolarLake, n.d). The scope for inventions are always there in the standards based integration strategies. The process of maturing for service oriented integration strategies is required to implement. Conclusions: In this paper, service oriented structure (SOA) has been discussed in the context of various related themes. Adoption of SOA showed growth enhancement as well as cost reduction for the organizations. Web services mostly work for improvement in different kinds of E-business. Total cost of ownership (TCO) for the loosely coupled architecture was best as compared to tightly coupled architecture. Benefits of standard based strategy integration were searched out as reduction of cost, agility, advantage of increased competitive, time to deliver product to market takes less time, consolidation, and alignment. References Bluenog. (2014). SOA/Integration. Available from: http://www.bluenog.com/solutions/soaintegration-solutions Accessed on 3/2/2014 Bos P.D. (2012). Principles of Service Oriented Architecture, Available from http://www.slideshare.net/omebos/principles-of-serviceoriented-architecture Accessed on 3/2/2014. Classon, P., Prem, J. (n.d) SOA: Integrating XML and Web Services A primer in Web Services and XML (Extensible Markup Language) Available from http://www.liquidhub.com/docs/Horizons_WSXML_primer_v3.pdf Accessed on 3/2/2014. Karatoprak, Y. (2012). Difference between Loose Coupling and Tight Coupling. Available from: http://www.c-sharpcorner.com/UploadFile/yusufkaratoprak/difference-between-loose-coupling-and-tight-coupling/ Accessed on 3/2/2014 PolarLake. (n.d) Standards-based Integration in Financial Services. Available from: http://www.polarlake.com/files/financial_services.pdf Accessed on 3/2/2014 Slama, D., Banke, K., and Krafzig, D. (2004). Service Oriented Architecture: Inventory of Distributed Computing Concepts. Available from: http://www.informit.com/articles/article.aspx?p=349749&seqNum=5 Accessed on 3/2/2014 Read More