Service-oriented architecture

Layer interaction in service-oriented architecture

In computing, there are many different definitions of Service Oriented Architecture (SOA), some of which are publicly known. SOA is an attempt to provide a set of principles or AC controller concepts that are used during the conditions of system development and integration. Such architecture attempts to package manipulation in the form of interoperable services in relation to those different business domains, which use it. Many departments or different organizations of a company can integrate or use such services-even if their personal client systems are quite different - the software modules may be available as a service. The SOA software module is an attempt to develop other types of integration. Rather than defining an API, SOA defines the interface in terms of protocols and functionality. An endpoint is an entry point for such a SOA implementation.

Service operating requires loose coupling of services in the operating system and requires other techniques that fall under the applications. SOA separates tasks into differentiated units, or services, which the developer provides in a network, so that users can combine and reuse them into the production of applications. These services interact with each other by passing data from one service to another or by coordinating an activity between two or more services.

SOA can be hypothesized as a type of continuity, which is in contrast to distributed computing or modular programming.

description introduction

The implementation of SOA depends on the software services network. The services include unrelated, loose coupled units of functionality, which do not hold calls to each other in them. Every service implements an action, such as filling an online application for an account, or viewing an online bank statement, or booking online or order airline tickets. Instead of services with calls to each other in their source code, they use defined protocols, which illustrate how services pass (flown) and parses messages using metadata details.

SOA Developers collaborate with individual SOA objects using orchestration. In the process of orchestration, the developer associates the software's functionality (services) in a non-hierarchical arrangement (in contrast to the class hierarchy). For this, he uses a software tool that includes a complete list of all available services, their features, as well as the means to build applications for using these sources.

To incorporate and activate all of these, it requires metadata containing enough details, which not only describes the characteristic properties of these services, but also describes the data that drives them. Programmers have made extensive use of XML in SOA for the structure of that data, which they put in almost a detailed description-container. Accordingly, the Web Services Describe Language (WSDL) typically describes the services themselves, while the SOAP protocol describes the transmission protocol. Are these descriptions the best choices for job descriptions and whether it will be made favorite in the future, there is a public discussion on this. As of 2008, SOA relies on data and services whose details are metadata, which should meet the following two criteria:

To create ad hoc applications (apps) created almost entirely from existing software services, enabling operators to keep a large fraction of the functionality together - this is the purpose of SOA. The larger the parts, the fewer interfacing points required to implement a set of functionality; However, large amounts of activity can not prove to be sufficient grainy for easy reuse. Every interface brings together some part of the processing overhead, so performance is considered in the selection of the granularity of services. The developmental possibilities of SOA indicate that the marginal cost of manufacturing n-th application is low, as all the necessary software is already present in order to satisfy the requirement of other applications (applications). Ideally, for the creation of a new application, now only requires orchestration.

To perform this, there should be no interaction between the chunks or between specified chunks. Instead, humans are inspired by the newly unpredictable requirements in relative ad-hoc manner, and specify the interaction of the services (all of these are unrelated partners). In this way, the needs of services are more in the form of larger units of functioning compared to traditional works or classes, otherwise the excessive complexity of such thousands of granular objects gives the application to the boz. Programmers develop services themselves using traditional languages ​​like Java, C, C ++, C # or COBOL.

Loose combination is a feature of SOA services, it is the opposite of those actions that linker together to build an executable, dynamically linked library or an assembly. SOA services also run in "safe" cover (such as Java or .NET) and manage allocation and correction of memory, permitting ad-hoc and delay in mobilization, and in some other programming languages ​​providing intermediary data typing for some extent.

In 2008, quite a third party software companies started offering software services for fee. In the future, SOA systems are likely to include third-party services that will be combined with in-house built-in services. It has the capability of spreading costs for many customers and customer applications and it promotes standardization both within and between industries. In particular, now there is a fully defined and documented set of both services and data in the travel industry, using the off-the-shelf software services, to enable any competent software engineer to build travel agency software Are there. Other industries, such as the finance industry, have also started making significant progress in this direction.

As an architecture, SOA relies on service orientation as its basic design element. If the service introduces a simple interface that separates the underlying complexity, users can use independent services without the knowledge of the platform's implementation of the service.

The SOA relies on services displaying its functionality through such interfaces which can be read by other applications and services and understand how to use these services.

The SOA objects often grow 100 to 1000 times relative to the specific practices of prior efforts to promote software reuse by using modularity of the works or using predefined action groups called the class. Requirements

To make efficient use of an SOA, it is necessary to meet the following requirements: theory

The following guiding principles define basic rules for the development, maintenance and use of SOA.

The following specific architectural principles are focused on specific styles in terms of design and service definitions that affect the internal behavior of a system and the style of its design:

The following provide additional ideas for defining an SOA implementation:

In addition, while defining an SOA implementation, the following factors / abilities can be considered. Web services approach

Web services can implement a service-oriented architecture. Web services make working block-blocking, accessible on standard Internet protocols independent of programming languages ​​and platforms. These services can either express new applications, or simply cover the existing system, so they become network-enabled.

Each SOA building block can play one or both roles. SOA and Web Service Protocols

The assessments normally use SOAs for those web service standards (e.g. SOAP) which have gained wide acceptance in the industry sector. These standards (also known as Web service specs) provide more interaction and proprietary software also provides some protection from the public-in for the software. However, SOA can be implemented using any service-based technology such as Genie, Corba or REST. Other SOA retention

Architectures can operate independently of specific techniques. Designers can implement SOA using a broad range of techniques, including:

Implementation can use one or more of these protocols, for example, they can use a file system system to communicate data according to the defined interfaces-specification between procedures corresponding to the SOA concept. There is an independent service with key defined interfaces, which can be used to perform their functions in a standard way, the service does not already have knowledge about the calling app, and the application does not have any knowledge about it. That's how the service really does its job. Many implementations of SOA have started, which are known to be based on SOA concepts of more advanced architecture known from SOA 2.0. Confidence adopt. Elements of SOA by Dirk Krafzig, Karl Banque and Dirk Slava SOA meta-model, The Linthicum Group, 2007 चित्र:SOMF V 2.0.jpg Service-Oriented Modeling Framework (SOMF) Version 2.0

SOA enables the development of applications that have been created with a combination of loose combination and interaction services.

These services interact on a formal definition (or contraction, e.g. WSDL) which is independent of the underlying platform and programming language. Interface definition hides the implementation of language-specific services. Therefore SOA-based systems work independently of development technologies and platforms (like Java, .NET etc.). Services written in C # Java running on the .NET platform and services running on the Java EE platform, for example, can both be consumed by a common mixed application (or client). Applications running on either platform can also consume services run on other web services that promote reuse. The managed environment can also cover COBOL's legacy system and offer them as software services. It has enhanced the useful life of many main systems in an infinite form, even if they have used any language originally.

Supports SOA integration and integration activities within complex enterprise systems, but SOA does not provide any method or framework for documenting capabilities and services.

High level languages ​​such as BPEL and specification such as WS-CDL and WS-coordinate service conceive the concept, for that they provide definition methods and provide support for orchestration in the more gross physical services of micro-particle services , Which can be inserted into architect work flow and business processes are implemented in composite applications or portals.

By 2008 researchers have begun investigating the use of service component architecture for the implementation of SOA.

Service Oriented Modeling is a SOA framework that guides the SOA practitioner to the concept, analysis, design and architect of its service-oriented property, which identifies different disciplines. The Service-Oriented Modeling Framework (SOMF) presents "maps" or a work structure describing different components, which contribute to a successful service-oriented modeling approach. It represents the key elements that identify the "what to do" aspect of the service development plan. This model enables the practitioner to create a project plan and helps identify the milestones of a service-oriented initiative. SOMF also provides a general modeling notation for alignment between business and IT organizations.

SOMF has been designed to meet the following principles: SOA Definitions

Commentators have provided several definitions of SOA. The Oasis group and the Open Group have both formulated formal definitions.

Oasis defines SOA as the following:

Use of distributed distributed capabilities and a pattern for the organization to be under the control of different ownership domains. It offers identical tools for proposing, searching, and interacting, and uses abilities to produce desired effects relevant to measurable pre-conditions and expectations. service contract

The following components are required for service contracts: All versions of the contract. Type - This is the type of service: it helps to differentiate those layers in which it remains. Types of service will vary for different implementations. Examples of service types include: Functional Non-functional SOA and Network Management Architecture

By 2008, the principles of SOA are being implemented in the area of ​​network management. Examples of service-oriented network management architecture include TS 188 001 NGN Management OSS Architecture from ETSI and the theory of M.3060 next-generation network management with ITU-T.

Tools for managing SOA infrastructure include: Discussion Benefit

Some Enterprise (Enterprise) Architects believe that SOA can help in quickly and cost-effectively contribute to the changing circumstances of the market. This style of architecture promotes reuse at macro (large service level) level rather than micro (small) class. This present makes it easy to use the internal contact of the IT (Legacy) property and its use.

In some contexts, the SOA can be considered to be successive evolution of architecture instead of a revolution. It retains many of the best practices of previous software architecture. For example, in communication systems, there have been very few developments in the field of solutions that truly use stable binding to talk about other devices. Formally adopting an SOA approach, such systems can prepare themselves to put pressure on the importance of well-defined, highly interactive interfaces.

Some people questioned whether SOA revives the concepts of modular programming (1970s), event-oriented design (1980s) or interface / component based design (1990s). The SOA service promotes the purpose of separating users (customers) from implementation. Therefore services can be run on different distributed platforms and may be available on the network. This can also maximize the reuse of the services. SOA is an architectural and design discipline that can enhance interaction capacity (exchange of information, reuse capacity and combination capacity), federation (integration of applications and sources keeping the personal autonomy and self-administration maintained). Designed to enhance the goal of increasing business and technology domain alignment.

Service Oriented Architecture (SOA) is an architectural approach (or style) for the creation of complex software-standard systems, which are universally formed from the groups of interconnected and interdependent building blocks. / p>

Through the use of analysis and design method at the time of the creation of services, SOA recovers its business and IT (IT) benefits. This method ensures that the services remain consistent with the architectural vision and plan and continue to follow the principles of service oriented. Arguments supporting SOAP trade and management aspects are given in many publications.

The only stand-alone unit of functionality available is available through the formally defined interface. Services can be a kind of "Nano enterprises (nano-enterprises)" which are easy to manufacture and improve. Other services may also be "large corporations", which are designed as a coordinated work of secondary services.

Services generally follow the following principles of service orientation:

The mature rollout of SOA effectively defines the organization's API.

Reasons to see the implementation of services as separate projects from big projects include:

Indirect benefits from SOA include a dramatically simplified test. Services are autonomous, non-existent, with fully documented interfaces and different from cross-cutting concerns of implementation. The industry has never passed through such circumstances anytime.

If there are appropriate defined test data in the organization, then when a service is being created, a related stub is created, which responds to test data. A whole set of regression tests, scripts, data and perception is also used for the service. The services which have been sought may also be tested as a 'black box' using the present stub. Where the services outside the primordial and radius are stub, while the remaining part of the trap is the test planner of the entire service, the testing environment is created. Since each interface is fully contained with documents, which is a complete set of retrograde test documentation, the identification of problems in test services becomes simpler. Testing is done only to find that the test service works according to its documentation and to find spaces between testing cases and documentation of existing services in the environment. Management of the data state of Idempotent services is the only complication.

In the documentation of the service, where it is useful, the examples are proved as shorthand. Documentation of some APIs in the Java community process provides good examples. Because these are elaborate, staff will typically use only important sub-sets. Within 'JSR-89' 'ossjsa.pdf' is such an example of a file. Challenges in adopting SOA

A clear and common challenge came to light, that is, the management of service metadata. SOA-based environments may include many services that exchange messages for work. According to the design, the only application can generate several million messages. Providing information on how services interact, and its management can be complicated. When these services are delivered by different organizations of the company or even by different companies (partners, suppliers, etc.) it becomes even more complex. This leads to big issues regarding trust in the teams (team) and therefore the SOA administration is presented.

The second challenge is the lack of testing in the SOA location. There are no advanced tools that provide testing capability of all the leadless services (which includes database services and messages with web services) in a specific architecture. Due to the lack of overall confidence, it is necessary that continuous testing of both the producer and consumer services continue. The main purpose of SOA is to provide business / quickness. Therefore it is important to invest in a test framework (construction or purchase), which will provide transparency to find the culprit in the architecture. To accelerate business, SOA services can be controlled by trading objectives and instructions according to the definition given in Business Motivation Model (BMM).

Another challenge is related to providing a level of security. When an application that other apps can use also exposes its capabilities in the form of AC services then the security models contained within the application are not sufficient. That is, application-managed security is not the right model for the security of services. Many new technologies and standards have started providing more suitable models for safety in the SOA. See SOA Security Entry for more information.

Since SOA and WS- * specification practitioners broaden, update and refine their output, they have to face the problem of lack of skilled people to work on SOA based systems, in the form of service structure and The integration of services is also included.

Intake is an important aspect of SOA implementation. The WS-I organization has developed Basic Profiles (BP) and Basic Security Profile (BSP) to emphasize compatibility. WS-I has designed test equipment to decide if web services are in accordance with WS-I profile guidelines. In addition, another charter has been set up to work on a trusted security profile.

Important seller promotions surround SOA; This creates expectations that may not be completed. Early adapters continued testing on development and runtime products in relation to real-world problems and this led to stack of product. Soya does not guarantee a reduction in IT costs, nor does it guarantee to accelerate the market or to improve the system. Successful SOA implementation can be all or some of these benefits, depending on the quality and affiliation of the system architecture and design.

Internal IT delivery organizations initiate regular SOA initiatives and some of them present concepts in business inappropriately, due to which misunderstandings remain. By adopting this, IT needs to meet the needs of IT delivery rather than trade, resulting in an organization with superlative laptop provisioning services, rather than an organization that responds quickly to market opportunities. Business leadership also agreed that this organization is implementing SOA properly.

The most important benefit of SOA is that it can be easily reused. Therefore ultimately accountability accountability and finance models should be developed in the organization. A business unit should be encouraged to create such services, which other units can use. On the contrary, units should be encouraged to reuse services. For this, some new components of administration are required: Criticism of SOA

Some criticisms of SOA depend on the SOA compilation with web services. For example, some critics claim that SOA results in an increase in XML layers, which tells XML parsing and structure. In the absence of the basic or binary forms of Remote Procedure Call (RPC), application speed may slow down and they require more processing capacity, which causes cost escalation. Most implementations include these overheads, but SOA can not be dependent on translation through remote process calls or XML, but can also be implemented using other technologies (for example, Java Business Integration, (JBI)). Emerging open source XML is generated from parsing technologies (like VTD-XML) and different XML-compatible binary formats that promise good performance of SOA.

Unstructured services require both consumer and provider to share the same consumer-specific , which are either included in it or are referred to by the message exchange between the consumer and the provider. The disadvantage of this obstacle is that if the service provider needs to maintain a shared context for each consumer, then it may reduce the overall measurement capacity of the service provider. This enhances the connectivity between the service provider and the consumer and makes service providers more difficult to change. Ultimately, some critics believe that SOA services are still highly interrupted by the applications they are expressing.

Another issue relates to the gradual development of WS- * standards and products (e.g. transaction, security), and as long as the SOA is fully managed and estimated with an additional budget and additional proof-of-concept for accidental work By doing so, SOA thus involves new risks.

Some critics believe that the SOA has the natural development of already well-built architectures (open interfaces, etc.) right now.

ITP system designs sometimes ignore the desirability of the converted system. Many systems with SOA-based systems, hard-code operations, goods and services of the organization, thus inhibit business agility in their online services and global markets.

The next step in the design process involves the definition of the Service Delivery Platform (SDP) and its implementation. In the SDP design phase, the business information model, identity management, products, materials, equipment and end user service characteristics, as well as what the system is so clever that it can keep pace with the success of business and its customers - these issues are defined . Extensions Services on SOA, Web 2.0, Messenger and Mesh

Web 2.0, which is the alleged "second generation" of web activity, has the ability to primarily collaborate and share information provided to viewers for sharing. Web 2.0 applications often use REST-ful web services and generally have AJAX based user interfaces that use web syndication, blogs and wikis. While there are no fixed standards for Web 2.0 on the one hand, it is characterized by the construction of existing web server architecture and services. That's why Web 2.0 also shows some SOA characteristics.

Some commentators consider mashups as Web 2.0 applications. The term "business meshp" was created to describe such web applications, which combine content from multiple sources, providing many characteristics of service-oriented business applications (SOBAs), integrated user experience. SOBAs are applications made from services in a narrative way. There is a dispute about "Conflicts of Web 2.0, Meshap and SOA", where some say that Web 2.0 applications are a realistic form of SOA mixing and business applications.

Web 2.0

Tim O'Reilly used the term "Web 2.0" to describe a set-up, fast-developing set of web-based applications. In a topic experiencing extensive coverage, the relationship between Web 2.0 and Service-oriented Architecture (SOAs) is included. SOA is considered as a philosophy with applications in the services with equally defined interfaces and is made publicly available through the search mechanism. The concealing of complexity and the issue of reuse and the concept of loose combination service prompted the researchers to take a closer look at the similarities between two views, SOA and Web 2.0, and their related applications. Some people say Web 2.0 and SOA are very different elements and thus they can not be called "parallel philosophy", while others believe that both the concepts are complementary and Web 2.0 is a global form of SOA.

Visions of Web 2.0 and SOA serve the user's different needs and thus explain the difference in terms of techniques and design used in real-world applications. However, by 2008, the use-cases have demonstrated the possibility of combining the principles and techniques of both Web 2.0 and SOA.

In a "Internet of the Services", all people, machines and accessories will be able to access tomorrow's (future) network infrastructure. In this way the Internet will offer services for all areas of life and business, such as virtual insurance, online banking and music and much more. These services will require a complex service framework, including service delivery platform that brings demand and supply together. The manufacturing units of the Internet include SOA, Web 2.0 and Technological Semantics; Also includes innovative business model and approach towards systemic and community based innovation.

Although Oracle indicates that Gartner is giving a new word, Gartner analysts have indicated that they call it a developed SOA and it will be named "SOA 2.0" Most of the major middle vendors (such as Red Hat, webMethods, TIBCO software, IBM, Sun Microsystems and Oracle) have had some form of SOA 2.0 properties over the years. डिजिटल तंत्रिका तंत्र (Digital Nervous System)

The SOA implementation is described as a representation of the vast nervous system known as the Digital Nervous System or Zero Latency Enterprise.

Also see them

साँचा:Software Engineering

wiki