644:
test data when a service is being built. A full set of regression tests, scripts, data, and responses is also captured for the service. The service can be tested as a 'black box' using existing stubs corresponding to the services it calls. Test environments can be constructed where the primitive and out-of-scope services are stubs, while the remainder of the mesh is test deployments of full services. As each interface is fully documented with its own full set of regression test documentation, it becomes simple to identify problems in test services. Testing evolves to merely validate that the test service operates according to its documentation, and finds gaps in documentation and test cases of all services within the environment. Managing the data state of
128:. This metadata describes both the functional characteristics of the service and quality-of-service characteristics. Service-oriented architecture aims to allow users to combine large chunks of functionality to form applications which are built purely from existing services and combining them in an ad hoc manner. A service presents a simple interface to the requester that abstracts away the underlying complexity acting as a black box. Further users can also access these independent services without any knowledge of their internal implementation.
2920:
601:
also develop enterprise-wide SOA that encapsulates a business-oriented infrastructure. SOA has also been illustrated as a highway system providing efficiency for car drivers. The point being that if everyone had a car, but there was no highway anywhere, things would be limited and disorganized, in any attempt to get anywhere quickly or efficiently. IBM Vice
President of Web Services Michael Liebow says that SOA "builds highways".
2344:
577:
569:
2910:
184:
668:; however, Web services are only one option to implement the patterns that comprise the SOA style. In the absence of native or binary forms of remote procedure call (RPC), applications could run more slowly and require more processing power, increasing costs. Most implementations do incur these overheads, but SOA can be implemented using technologies (for example,
767:
similarities between the two philosophies, SOA and Web 2.0, and their respective applications. Some argue Web 2.0 and SOA have significantly different elements and thus can not be regarded "parallel philosophies", whereas others consider the two concepts as complementary and regard Web 2.0 as the global SOA.
600:
With SOA, the idea is that an organization can look at a problem holistically. A business has more overall control. Theoretically there would not be a mass of developers using whatever tool sets might please them. But rather they would be coding to a standard that is set within the business. They can
506:
perform their tasks in a standard way, without a service having foreknowledge of the calling application, and without the application having or needing knowledge of how the service actually performs its tasks. SOA enables the development of applications that are built by combining loosely coupled and
146:
between services. SOA separates functions into distinct units, or services, which developers make accessible over a network in order to allow users to combine and reuse them in the production of applications. These services and their corresponding consumers communicate with each other by passing data
770:
The philosophies of Web 2.0 and SOA serve different user needs and thus expose differences with respect to the design and also the technologies used in real-world applications. However, as of 2008, use-cases demonstrated the potential of combining technologies and principles of both Web 2.0 and SOA.
843:
Interactive applications requiring real-time response times, for example low-latency interactive 3d applications, are using specific service oriented architectures addressing the specific needs of such kind of applications. These include for example low-latency optimized distributed computation and
766:
SOA is the philosophy of encapsulating application logic in services with a uniformly defined interface and making these publicly available via discovery mechanisms. The notion of complexity-hiding and reuse, but also the concept of loosely coupling services has inspired researchers to elaborate on
696:
A primary challenge faced by service-oriented architecture is managing of metadata. Environments based on SOA include many services which communicate among each other to perform tasks. Due to the fact that the design may involve multiple services working in conjunction, an
Application may generate
643:
SOA promises to simplify testing indirectly. Services are autonomous, stateless, with fully documented interfaces, and separate from the cross-cutting concerns of the implementation. If an organization possesses appropriately defined test data, then a corresponding stub is built that reacts to the
560:
offers a modeling language and a work structure or "map" depicting the various components that contribute to a successful service-oriented modeling approach. It illustrates the major elements that identify the "what to do" aspects of a service development scheme. The model enables practitioners to
505:
Implementations can use one or more of these protocols and, for example, might use a file-system mechanism to communicate data following a defined interface specification between processes conforming to the SOA concept. The key is independent services with defined interfaces that can be called to
375:
It locates entries in the broker registry using various find operations and then binds to the service provider in order to invoke one of its web services. Whichever service the service-consumers need, they have to take it into the brokers, bind it with respective service and then use it. They can
360:
Its main functionality is to make information regarding the web service available to any potential requester. Whoever implements the broker decides the scope of the broker. Public brokers are available anywhere and everywhere but private brokers are only available to a limited amount of public.
522:
platforms, for example, can both be consumed by a common composite application (or client). Applications running on either platform can also consume services running on the other as web services that facilitate reuse. Managed environments can also wrap COBOL legacy systems and present them as
620:
A service comprises a stand-alone unit of functionality available only via a formally defined interface. Services can be some kind of "nano-enterprises" that are easy to produce and improve. Also services can be "mega-corporations" constructed as the coordinated work of subordinate services.
608:
of previous software architectures. In communications systems, for example, little development of solutions that use truly static bindings to talk to other equipment in the network has taken place. By embracing a SOA approach, such systems can position themselves to stress the importance of
692:
of the service provider if the service-provider needs to retain the shared context for each consumer. It also increases the coupling between a service provider and a consumer and makes switching service providers more difficult. Ultimately, some critics feel that SOA services are still too
410:. This is done to make the functional building-blocks accessible over standard Internet protocols that are independent of platforms and programming languages. These services can represent either new applications or just wrappers around existing legacy systems to make them network-enabled.
651:
Examples may prove useful to aid in documenting a service to the level where it becomes useful. The documentation of some APIs within the Java
Community Process provide good examples. As these are exhaustive, staff would typically use only important subsets. The 'ossjsa.pdf' file within
628:
Separation promotes the concept to the business that services can be delivered quickly and independently from the larger and slower-moving projects common in the organization. The business starts understanding systems and simplified user interfaces calling on services. This advocates
687:
Stateful services require both the consumer and the provider to share the same consumer-specific context, which is either included in or referenced by messages exchanged between the provider and the consumer. This constraint has the drawback that it could reduce the overall
349:
It creates a web service and provides its information to the service registry. Each provider debates upon a lot of hows and whys like which service to expose, which to give more importance: security or easy availability, what price to offer the service for and many
1713:
109:), an interface or communication protocol between different parts of a computer program intended to simplify the implementation and maintenance of software. An API can be thought of as the service, and the SOA the architecture that allows the service to operate.
62:
over a network. A service is a discrete unit of functionality that can be accessed remotely and acted upon and updated independently, such as retrieving a credit card statement online. SOA is also intended to be independent of vendors, products and technologies.
102:. Service-oriented architecture integrates distributed, separately maintained and deployed software components. It is enabled by technologies and standards that facilitate components' communication and cooperation over a network, especially over an IP network.
801:, which aid in encapsulating choice of language and frameworks, making their choice a concern internal to the service. Microservices are a new realisation and implementation approach to SOA, which have become popular since 2014 (and after the introduction of
541:
extend the service concept by providing a method of defining and supporting orchestration of fine-grained services into more coarse-grained business services, which architects can in turn incorporate into workflows and business processes implemented in
517:
of the language-specific service. SOA-based systems can therefore function independently of development technologies and platforms (such as Java, .NET, etc.). Services written in C# running on .NET platforms and services written in Java running on
2334:
700:
Another major problem faced by SOA is the lack of a uniform testing framework. There are no tools that provide the required features for testing these services in a service-oriented architecture. The major causes of difficulty are:
1717:
261:
Services should be designed to be long lived. Where possible services should avoid forcing consumers to change if they do not require new features, if you call a service today you should be able to call the same service
229:
There are no industry standards relating to the exact composition of a service-oriented architecture, although many industry sources have published their own principles. Some of these include the following:
2332:
763:" to describe a perceived, quickly growing set of web-based applications. A topic that has experienced extensive coverage involves the relationship between Web 2.0 and service-oriented architectures.
300:
Services are decomposed or consolidated (normalized) to minimize redundancy. In some, this may not be done. These are the cases where performance optimization, access, and aggregation are required.
421:) also provide greater interoperability and some protection from lock-in to proprietary vendor software. One can, however, also implement SOA using any other service-based technology, such as
2005:
Dragoni, Nicola; Giallorenzo, Saverio; Alberto Lluch
Lafuente; Mazzara, Manuel; Montesi, Fabrizio; Mustafin, Ruslan; Safina, Larisa (2016). "Microservices: yesterday, today, and tomorrow".
2333:
697:
millions of messages. Further services may belong to different organizations or even competing firms creating a huge trust issue. Thus SOA governance comes into the scheme of things.
513:
These services inter-operate based on a formal definition (or contract, e.g., WSDL) that is independent of the underlying platform and programming language. The interface definition
1571:
Brandner, M., Craes, M., Oellermann, F., Zimmermann, O., Web
Services-Oriented Architecture in Production in the Finance Industry, Informatik-Spektrum 02/2004, Springer-Verlag, 2004
354:
The provider also has to decide what category the service should be listed in for a given broker service and what sort of trading partner agreements are required to use the service.
636:
Separation promotes the decoupling of services from consuming projects. This encourages good design insofar as the service is designed without knowing who its consumers are.
556:
is an SOA framework that identifies the various disciplines that guide SOA practitioners to conceptualize, analyze, design, and architect their service-oriented assets. The
417:, which has gained broad industry acceptance after the recommendation of Version 1.2 from the W3C (World Wide Web Consortium) in 2003. These standards (also referred to as
565:
and to identify the milestones of a service-oriented initiative. SOMF also provides a common modeling notation to address alignment between business and IT organizations.
639:
Documentation and test artifacts of the service are not embedded within the detail of the larger project. This is important when the service needs to be reused later.
1581:
680:(DDS)) that do not depend on remote procedure calls or translation through XML or JSON. At the same time, emerging open-source XML parsing technologies (such as
597:
promotes reuse at the macro (service) level rather than micro (classes) level. It can also simplify interconnection to—and usage of—existing IT (legacy) assets.
1117:
394:. Lower level enterprise integration patterns that are not bound to a particular architectural style continue to be relevant and eligible in SOA design.
1213:
1366:
Duan, Yucong; Narendra, Nanjangud; Du, Wencai; Wang, Yongzhi; Zhou, Nianjun (2014). "Exploring Cloud
Service Brokering from an Interface Perspective".
2949:
1489:
1874:
444:
Architectures can operate independently of specific technologies and can therefore be implemented using a wide range of technologies, including:
2959:
2396:
112:
Note that
Service-Oriented Architecture must not be confused with Service Based Architecture as those are two different architectural styles.
808:
There is no single commonly agreed definition of microservices. The following characteristics and principles can be found in the literature:
17:
889:
1095:
391:
2954:
1631:
557:
1413:
2012 13th ACIS International
Conference on Software Engineering, Artificial Intelligence, Networking and Parallel/Distributed Computing
294:
A principle to ensure services have an adequate size and scope. The functionality provided by the service to the user must be relevant.
1697:
2349:
968:
1848:
2260:
1904:
1955:
593:
believe that SOA can help businesses respond more quickly and more cost-effectively to changing market conditions. This style of
2042:
1016:
2913:
2779:
2708:
2283:
2230:
2122:
1432:
1387:
1341:
1184:
1151:
1055:
919:
2602:
2505:
1663:
897:
748:
Application programming interfaces (APIs) are the frameworks through which developers can interact with a web application.
610:
604:
In some respects, SOA could be regarded as an architectural evolution rather than as a revolution. It captures many of the
66:
Service orientation is a way of thinking in terms of services and service-based development and the outcomes of services.
2389:
1512:
1079:
952:
743:
418:
278:
Services are independent and control the functionality they encapsulate, from a Design-time and a run-time perspective.
2944:
2582:
2449:
2434:
2166:
853:
519:
286:
Services are stateless, that is either return the requested value or give an exception hence minimizing resource use.
106:
2151:
COM.Geo '11: Proceedings of the 2nd
International Conference on Computing for Geospatial Research & Applications
1781:
1757:
1805:
673:
483:
328:
316:
Services are supplemented with communicative meta data by which they can be effectively discovered and interpreted.
1929:
883:
653:
526:
461:
434:
387:
303:
281:
159:
2738:
2665:
2655:
2500:
2429:
478:
430:
2923:
2789:
2718:
2382:
1217:
868:
381:
319:
289:
234:
2728:
2587:
2454:
1239:
2650:
2645:
2459:
255:
Services can be called from anywhere within the network that it is located no matter where it is present.
249:
The relationship between services is minimized to the level that they are only aware of their existence.
2845:
2693:
2688:
2640:
2617:
2597:
1882:
1298:
624:
Reasons for treating the implementation of services as separate projects from larger projects include:
333:
Many services which were not initially planned under SOA, may get encapsulated or become a part of SOA.
273:
205:
2850:
2840:
2368:
1740:
863:
732:
677:
669:
553:
467:
1549:
2753:
2552:
2535:
2444:
473:
83:
for its consumers, meaning the consumer does not have to be aware of the service's inner workings.
2703:
2547:
2102:
798:
59:
1299:"4.4 Guidelines for Using Web Service Contract Technologies - Anatomy of a Web Service Contract"
2758:
2515:
2510:
1544:
1176:
543:
366:
239:
Services adhere to a standard communications agreement, as defined collectively by one or more
147:
in a well-defined, shared format, or by coordinating an activity between two or more services.
55:
1529:
1143:
684:) and various XML-compatible binary formats promise to significantly improve SOA performance.
2964:
2577:
2530:
1483:
878:
786:
714:
151:
95:
1168:
1135:
2875:
2713:
2572:
2562:
2474:
2419:
2405:
2364:
1455:
816:
590:
31:
785:
Microservices are a modern interpretation of service-oriented architectures used to build
8:
2895:
2880:
2748:
2612:
2520:
2464:
2199:"Service Oriented Interactive Media (SOIM) Engines Enabled by Optimized Resource Sharing"
2147:"Service-oriented interactive 3D visualization of massive 3D city models on thin clients"
976:
790:
265:
240:
155:
137:
99:
1326:
IEEE International
Conference on Services Computing, 2004. (SCC 2004). Proceedings. 2004
1257:
270:
The services act as black boxes, that is their inner logic is hidden from the consumers.
2885:
2525:
2297:
2289:
2236:
2172:
2083:
2006:
1975:
1438:
1393:
1347:
1024:
514:
47:
2027:
2799:
2557:
2279:
2226:
2162:
2118:
2075:
2043:"Microservices Architecture Enables DevOps: Migration to a Cloud-Native Architecture"
1983:
1508:
1428:
1383:
1337:
1180:
1169:
1147:
1136:
1111:
1075:
1051:
948:
547:
311:
43:
2176:
2087:
1397:
1351:
2870:
2814:
2592:
2484:
2479:
2271:
2240:
2216:
2208:
2154:
2110:
2065:
2057:
1979:
1967:
1554:
1469:
1442:
1420:
1375:
1329:
998:
794:
613:
and Object-Oriented Analysis and Design (OOAD) of remote objects, for instance, in
2293:
609:
well-defined, highly inter-operable interfaces. Other predecessors of SOA include
2890:
2743:
2723:
2607:
2469:
2146:
2114:
1809:
1785:
1761:
1667:
756:
538:
167:
121:
51:
1660:
1608:
150:
SOA can be seen as part of the continuum which ranges from the older concept of
73:
It logically represents a repeatable business activity with a specified outcome.
2794:
2698:
2439:
2198:
2004:
1826:
1558:
1255:
873:
858:
633:. That is to say, it fosters business innovations and speeds up time-to-market.
142:
2202:
2103:"A Service-Oriented Interface for Highly Interactive Distributed Applications"
1530:"Compliance by design – Bridging the chasm between auditors and IT architects"
1528:
Julisch, Klaus; Suter, Christophe; Woitalla, Thomas; Zimmermann, Olaf (2011).
838:
413:
Implementers commonly build SOAs using web services standards. One example is
2938:
2774:
2542:
2079:
1702:
University of Applied Science of Northwestern Switzerland, School of Business
1333:
805:), and which also emphasize continuous deployment and other agile practices.
780:
605:
507:
489:
407:
2158:
2809:
2804:
2733:
2352:
was created from a revision of this article dated 27 October 2011
2275:
2221:
2070:
708:
Huge set of testing combinations due to integration of autonomous services.
562:
448:
209:
91:
69:
A service has four properties according to one of many definitions of SOA:
42:) is an architectural style that focuses on discrete services instead of a
2261:"Service Oriented Device Integration - an Analysis of SOA Design Patterns"
717:
is continuously changing due to availability of new features and services.
2212:
1971:
1778:
1754:
1424:
1379:
689:
665:
403:
2259:
Mauro, Christian; Leimeister, Jan Marco; Krcmar, Helmut (January 2010).
1956:"Web 2.0 and SOA: Converging Concepts Enabling the Internet of Services"
1802:
2819:
2784:
2374:
2109:. Lecture Notes in Computer Science. Vol. 6043. pp. 266–277.
2061:
1714:"JSR-000089 OSS Service Activation API Specification 1.0 Final Release"
1474:
1457:
1282:
1214:"Application Platform Strategies Blog: SOA is Dead; Long Live Services"
645:
2011:
1138:
Service-Oriented Modeling: Service Analysis, Design, and Architecture
384:, which has a business part, a functional part and a technical part.
198:
80:
1456:
Olaf Zimmermann, Cesare Pautasso, Gregor Hohpe, Bobby Woolf (2016).
2567:
1849:"SOA services still too constrained by applications they represent"
1324:
Tony Shan (2004). "Building a service-oriented eBanking platform".
797:
in order to fulfill a goal. These services use technology agnostic
486:(Microsoft's implementation of Web services, forming a part of WCF)
376:
access multiple services if the service provides multiple services.
194:
125:
1905:"How to Efficiently Test Service Oriented Architecture | WSO2 Inc"
1134:
Michael Bell (2008). "Introduction to Service-Oriented Modeling".
1098:. December 9, 2008. Archived from the original on December 9, 2008
2204:
2016 IEEE Symposium on Service-Oriented System Engineering (SOSE)
1171:
SOA Modeling Patterns for Service-Oriented Discovery and Analysis
760:
681:
630:
464:(REST) constituting its own constraints-based architectural style
324:
Logic is divided into various services, to promote reuse of code.
576:
2424:
1683:
Elizabeth Millard (January 2005). "Building a Better Process".
812:
fine-grained interfaces (to independently deployable services),
802:
568:
534:
499:
1527:
1072:
Fundamentals of Software Architecture: An Engineering Approach
945:
Fundamentals of Software Architecture: An Engineering Approach
365:
was an early, no longer actively supported attempt to provide
2624:
1852:
1632:". "Case Study of System Architecture that use COBOL assets""
614:
426:
2268:
2010 43rd Hawaii International Conference on System Sciences
2144:
1953:
572:
Elements of SOA, by Dirk Krafzig, Karl Banke, and Dirk Slama
380:
The service consumer–provider relationship is governed by a
2835:
2041:
Balalaie, A.; Heydarnoori, A.; Jamshidi, P. (May 1, 2016).
2040:
1779:"i-Technology Viewpoint: The Performance Woe of Binary XML"
1416:
1371:
1286:
844:
communication as well as resource and instance management.
839:
Service-oriented architectures for interactive applications
711:
Inclusion of services from different and competing vendors.
530:
494:
452:
438:
422:
414:
362:
252:
Service location transparency (an aspect of loose coupling)
163:
1216:. Apsblog.burtongroup.com. January 5, 2009. Archived from
999:"Service-Oriented Architecture Standards - The Open Group"
2100:
2025:
1586:
342:
Each SOA building block can play any of the three roles:
1256:
Microsoft Windows Communication Foundation team (2012).
246:
Service reference autonomy (an aspect of loose coupling)
54:
where services are provided to the other components by
2196:
1827:"The Reason SOA Isn't Delivering Sustainable Software"
1096:"Migrating to a service-oriented architecture, Part 1"
402:
Service-oriented architecture can be implemented with
357:
Service broker, service registry or service repository
120:
In SOA, services use protocols that describe how they
2258:
1411:
Duan, Yucong (2012). "A Survey on Service Contract".
737:
50:. By consequence, it is also applied in the field of
90:Different services can be used in conjunction as a
1368:2014 IEEE International Conference on Web Services
1365:
390:have two broad, high-level architectural styles:
2936:
1116:: CS1 maint: bot: original URL status unknown (
969:"Chapter 1: Service Oriented Architecture (SOA)"
308:Services can be used to compose other services.
789:. Services in a microservice architecture are
2390:
1458:"A Decade of Enterprise Integration Patterns"
1287:eight specific service-orientation principles
457:Messaging, e.g., with ActiveMQ, JMS, RabbitMQ
2019:
1502:
1488:: CS1 maint: multiple names: authors list (
1166:
1133:
890:Service-oriented development of applications
726:
693:constrained by applications they represent.
397:
2397:
2383:
2107:European Conference on Parallel Processing
1738:
793:that communicate with each other over the
721:
584:
558:Service-oriented modeling framework (SOMF)
170:(which some see as the offspring of SOA).
2220:
2069:
2010:
1741:"Bray: SOA too complex; 'just vendor BS'"
1548:
1473:
1449:
1323:
894:Service-oriented distributed applications
705:Heterogeneity and complexity of solution.
580:SOA meta-model, The Linthicum Group, 2007
243:documents within a given set of services.
2950:Architectural pattern (computer science)
2588:Software development process/methodology
2404:
2360:, and does not reflect subsequent edits.
2343:
1629:
1297:
834:DevOps with holistic service monitoring.
575:
567:
94:to provide the functionality of a large
27:Architectural pattern in software design
2145:Dieter Hildebrandt; Jan Klimke (2011).
1954:Christoph Schroth; Till Janner (2007).
1803:"Manipulate XML Content the Ximple Way"
1258:"Principles of Service Oriented Design"
14:
2937:
1949:
1947:
1129:
1127:
831:decentralized continuous delivery, and
822:IDEAL cloud application architectures,
158:, through SOA, and on to practices of
105:SOA is related to the idea of an API (
2960:Service-oriented (business computing)
2378:
1160:
1048:Cloud Computing: A Practical Approach
1045:
825:polyglot programming and persistence,
124:and parse messages using description
86:It may be composed of other services.
2909:
2603:Software verification and validation
2506:Component-based software engineering
2190:
2138:
2101:Frank Glinka; Allaithy Raed (2009).
2094:
1696:Brayan Zimmerli (November 11, 2009)
1611:(in Japanese). W3.org. June 24, 2003
1410:
1275:
914:
912:
898:Web Application Description Language
611:Component-based software engineering
177:
131:
1944:
1609:"SOAP Version 1.2 の公開について (W3C 勧告)"
1193:
1124:
24:
2955:Enterprise application integration
2330:
1932:. Tim O'Reilly. September 30, 2005
1755:"Index XML Documents with VTD-XML"
1661:A New Blueprint For The Enterprise
815:business-driven development (e.g.
744:Application programming interfaces
738:Application programming interfaces
25:
2976:
2583:Software configuration management
2450:Search-based software engineering
2435:Experimental software engineering
2197:Mahy Aly; Michael Franke (2016).
1829:. jpmorgenthal.com. June 19, 2009
909:
854:Application programming interface
828:lightweight container deployment,
648:services is the only complexity.
107:application programming interface
2919:
2918:
2908:
2342:
1753:Jimmy Zhang (February 20, 2008)
920:"SOA Source Book - What Is SOA?"
774:
674:Windows Communication Foundation
527:High-level programming languages
182:
2034:
2026:James Lewis and Martin Fowler.
1998:
1922:
1897:
1867:
1841:
1819:
1801:Jimmy Zhang (January 9, 2008)
1795:
1771:
1747:
1732:
1716:. July 26, 2011. Archived from
1706:
1690:
1677:
1653:
1641:
1623:
1601:
1574:
1565:
1521:
1496:
1404:
1359:
1317:
1291:
1249:
1232:
1206:
884:Service-oriented communications
462:Representational state transfer
2430:Empirical software engineering
1240:Improve your SOA project plans
1088:
1064:
1039:
1009:
991:
961:
937:
479:Internet Communications Engine
431:Internet Communications Engine
392:choreography and orchestration
197:format but may read better as
98:, a principle SOA shares with
13:
1:
1777:Jimmy Zhang (August 5, 2008)
903:
869:Service granularity principle
382:standardized service contract
235:Standardized service contract
173:
36:service-oriented architecture
18:Service Oriented Architecture
2455:Site reliability engineering
2115:10.1007/978-3-642-14122-5_31
1503:Rotem-Gal-Oz, Arnon (2012).
1175:. Wiley & Sons. p.
1142:. Wiley & Sons. p.
787:distributed software systems
664:SOA has been conflated with
659:
388:Service composition patterns
7:
2460:Social software engineering
1630:Okishima, Haruhiru (2006).
924:collaboration.opengroup.org
847:
533:and specifications such as
337:
115:
46:. SOA is a good choice for
10:
2981:
2598:Software quality assurance
1559:10.1016/j.cose.2011.03.005
1046:Velte, Anthony T. (2010).
778:
751:
741:
730:
419:web service specifications
372:Service requester/consumer
2904:
2863:
2828:
2767:
2681:
2674:
2633:
2493:
2412:
1666:January 16, 2009, at the
864:OASIS SOA Reference Model
733:Event-driven architecture
727:Event-driven architecture
678:data distribution service
670:Java Business Integration
656:exemplifies such a file.
554:Service-oriented modeling
468:Data Distribution Service
398:Implementation approaches
2945:Software design patterns
2754:Model-driven engineering
2553:Functional specification
2536:Software incompatibility
2445:Requirements engineering
1784:January 9, 2020, at the
1698:Business Benefits of SOA
1537:Computers & Security
1507:. Manning Publications.
1334:10.1109/SCC.2004.1358011
1203:. Serviceorientation.org
1199:Thomas Erl (June 2005).
1074:. O'Reilly Media. 2020.
947:. O'Reilly Media. 2020.
515:hides the implementation
2548:Enterprise architecture
2159:10.1145/1999320.1999326
722:Extensions and variants
585:Organizational benefits
206:converting this article
2759:Round-trip engineering
2516:Backward compatibility
2511:Software compatibility
2338:
2318:Listen to this article
2276:10.1109/HICSS.2010.336
1808:July 30, 2017, at the
581:
573:
544:composite applications
367:Web services discovery
60:communication protocol
56:application components
2578:Software architecture
2531:Forward compatibility
2337:
1790:Microservices Journal
1760:July 4, 2008, at the
1650:. Prentice Hall, 2005
1167:Michael Bell (2010).
879:Software architecture
591:enterprise architects
579:
571:
304:Service composability
297:Service normalization
282:Service statelessness
152:distributed computing
136:The related buzzword
76:It is self-contained.
2876:Computer engineering
2573:Software archaeology
2563:Programming paradigm
2475:Software maintenance
2420:Computer programming
2406:Software engineering
2369:More spoken articles
2213:10.1109/SOSE.2016.47
2207:. pp. 231–237.
1972:10.1109/MITP.2007.60
1425:10.1109/SNPD.2012.22
1419:. pp. 805–810.
1380:10.1109/ICWS.2014.55
1374:. pp. 329–336.
1328:. pp. 237–244.
1285:of SOA Systems Inc.
1201:About the Principles
817:domain-driven design
96:software application
32:software engineering
2896:Systems engineering
2881:Information science
2661:Service orientation
2613:Structured analysis
2521:Compatibility layer
2465:Software deployment
2303:on January 24, 2022
1986:on December 3, 2013
1220:on January 15, 2009
523:software services.
460:RESTful HTTP, with
320:Service reusability
290:Service granularity
266:Service abstraction
241:service description
156:modular programming
138:service-orientation
100:modular programming
2886:Project management
2651:Object orientation
2618:Essential analysis
2526:Compatibility mode
2339:
2062:10.1109/MS.2016.64
1875:"Governance Layer"
1475:10.1109/MS.2016.11
1262:msdn.microsoft.com
1027:on August 19, 2016
973:msdn.microsoft.com
582:
574:
451:based on WSDL and
208:, if appropriate.
48:system integration
2932:
2931:
2859:
2858:
2800:Information model
2704:Incremental model
2558:Modeling language
2335:
2285:978-1-4244-5509-6
2270:. pp. 1–10.
2232:978-1-5090-2253-3
2124:978-3-642-14121-8
1930:"What Is Web 2.0"
1879:www.opengroup.org
1659:Christopher Koch
1434:978-1-4673-2120-4
1389:978-1-4799-5054-6
1343:978-0-7695-2225-8
1186:978-0-470-48197-4
1153:978-0-470-14111-3
1057:978-0-07-162694-1
1021:www.opengroup.org
1003:www.opengroup.org
759:coined the term "
312:Service discovery
258:Service longevity
227:
226:
132:Defining concepts
44:monolithic design
16:(Redirected from
2972:
2922:
2921:
2912:
2911:
2871:Computer science
2679:
2678:
2593:Software quality
2485:Systems analysis
2480:Software testing
2399:
2392:
2385:
2376:
2375:
2359:
2357:
2346:
2345:
2336:
2326:
2324:
2319:
2312:
2310:
2308:
2302:
2296:. Archived from
2265:
2252:
2251:
2249:
2247:
2224:
2194:
2188:
2187:
2185:
2183:
2142:
2136:
2135:
2133:
2131:
2098:
2092:
2091:
2073:
2047:
2038:
2032:
2031:
2023:
2017:
2016:
2014:
2002:
1996:
1995:
1993:
1991:
1982:. Archived from
1951:
1942:
1941:
1939:
1937:
1926:
1920:
1919:
1917:
1915:
1901:
1895:
1894:
1892:
1890:
1881:. Archived from
1871:
1865:
1864:
1862:
1860:
1845:
1839:
1838:
1836:
1834:
1823:
1817:
1799:
1793:
1775:
1769:
1751:
1745:
1744:
1739:Joe McKendrick.
1736:
1730:
1729:
1727:
1725:
1720:on July 26, 2011
1710:
1704:
1694:
1688:
1681:
1675:
1657:
1651:
1645:
1639:
1638:
1636:
1627:
1621:
1620:
1618:
1616:
1605:
1599:
1598:
1596:
1594:
1578:
1572:
1569:
1563:
1562:
1552:
1543:(6–7): 410–426.
1534:
1525:
1519:
1518:
1500:
1494:
1493:
1487:
1479:
1477:
1453:
1447:
1446:
1408:
1402:
1401:
1363:
1357:
1355:
1321:
1315:
1314:
1312:
1310:
1295:
1289:
1279:
1273:
1272:
1270:
1268:
1253:
1247:
1236:
1230:
1229:
1227:
1225:
1210:
1204:
1197:
1191:
1190:
1174:
1164:
1158:
1157:
1141:
1131:
1122:
1121:
1115:
1107:
1105:
1103:
1092:
1086:
1085:
1068:
1062:
1061:
1043:
1037:
1036:
1034:
1032:
1023:. Archived from
1013:
1007:
1006:
995:
989:
988:
986:
984:
975:. Archived from
965:
959:
958:
941:
935:
934:
932:
930:
916:
346:Service provider
274:Service autonomy
222:
219:
213:
204:You can help by
186:
185:
178:
21:
2980:
2979:
2975:
2974:
2973:
2971:
2970:
2969:
2935:
2934:
2933:
2928:
2900:
2891:Risk management
2855:
2824:
2763:
2744:Waterfall model
2714:Prototype model
2709:Iterative model
2670:
2646:Aspect-oriented
2629:
2608:Software system
2489:
2470:Software design
2408:
2403:
2373:
2372:
2361:
2355:
2353:
2350:This audio file
2347:
2340:
2331:
2328:
2322:
2321:
2317:
2306:
2304:
2300:
2286:
2263:
2255:
2245:
2243:
2233:
2222:1854/LU-7215326
2195:
2191:
2181:
2179:
2169:
2143:
2139:
2129:
2127:
2125:
2099:
2095:
2045:
2039:
2035:
2028:"Microservices"
2024:
2020:
2003:
1999:
1989:
1987:
1960:IT Professional
1952:
1945:
1935:
1933:
1928:
1927:
1923:
1913:
1911:
1903:
1902:
1898:
1888:
1886:
1885:on June 4, 2016
1873:
1872:
1868:
1858:
1856:
1855:. June 27, 2009
1847:
1846:
1842:
1832:
1830:
1825:
1824:
1820:
1810:Wayback Machine
1800:
1796:
1786:Wayback Machine
1776:
1772:
1762:Wayback Machine
1752:
1748:
1737:
1733:
1723:
1721:
1712:
1711:
1707:
1695:
1691:
1682:
1678:
1674:, March 1, 2005
1668:Wayback Machine
1658:
1654:
1646:
1642:
1634:
1628:
1624:
1614:
1612:
1607:
1606:
1602:
1592:
1590:
1580:
1579:
1575:
1570:
1566:
1550:10.1.1.390.3652
1532:
1526:
1522:
1515:
1501:
1497:
1481:
1480:
1454:
1450:
1435:
1409:
1405:
1390:
1364:
1360:
1344:
1322:
1318:
1308:
1306:
1305:. June 11, 2021
1296:
1292:
1280:
1276:
1266:
1264:
1254:
1250:
1246:, July 16, 2004
1237:
1233:
1223:
1221:
1212:
1211:
1207:
1198:
1194:
1187:
1165:
1161:
1154:
1132:
1125:
1109:
1108:
1101:
1099:
1094:
1093:
1089:
1082:
1070:
1069:
1065:
1058:
1050:. McGraw Hill.
1044:
1040:
1030:
1028:
1015:
1014:
1010:
997:
996:
992:
982:
980:
979:on July 7, 2017
967:
966:
962:
955:
943:
942:
938:
928:
926:
918:
917:
910:
906:
850:
841:
783:
777:
754:
746:
740:
735:
729:
724:
662:
587:
539:WS-Coordination
400:
340:
223:
217:
214:
203:
187:
183:
176:
168:cloud computing
134:
118:
52:software design
28:
23:
22:
15:
12:
11:
5:
2978:
2968:
2967:
2962:
2957:
2952:
2947:
2930:
2929:
2927:
2926:
2916:
2905:
2902:
2901:
2899:
2898:
2893:
2888:
2883:
2878:
2873:
2867:
2865:
2864:Related fields
2861:
2860:
2857:
2856:
2854:
2853:
2848:
2843:
2838:
2832:
2830:
2826:
2825:
2823:
2822:
2817:
2812:
2807:
2802:
2797:
2795:Function model
2792:
2787:
2782:
2777:
2771:
2769:
2765:
2764:
2762:
2761:
2756:
2751:
2746:
2741:
2736:
2731:
2726:
2721:
2716:
2711:
2706:
2701:
2699:Executable UML
2696:
2691:
2685:
2683:
2676:
2672:
2671:
2669:
2668:
2663:
2658:
2653:
2648:
2643:
2637:
2635:
2631:
2630:
2628:
2627:
2622:
2621:
2620:
2610:
2605:
2600:
2595:
2590:
2585:
2580:
2575:
2570:
2565:
2560:
2555:
2550:
2545:
2540:
2539:
2538:
2533:
2528:
2523:
2518:
2508:
2503:
2497:
2495:
2491:
2490:
2488:
2487:
2482:
2477:
2472:
2467:
2462:
2457:
2452:
2447:
2442:
2440:Formal methods
2437:
2432:
2427:
2422:
2416:
2414:
2410:
2409:
2402:
2401:
2394:
2387:
2379:
2362:
2348:
2341:
2329:
2316:
2315:
2314:
2313:
2284:
2254:
2253:
2231:
2189:
2167:
2137:
2123:
2093:
2033:
2018:
1997:
1943:
1921:
1896:
1866:
1840:
1818:
1794:
1770:
1746:
1731:
1705:
1689:
1676:
1652:
1648:Enterprise SOA
1640:
1622:
1600:
1573:
1564:
1520:
1514:978-1933988269
1513:
1495:
1448:
1433:
1403:
1388:
1358:
1342:
1316:
1290:
1281:Principles by
1274:
1248:
1238:Yvonne Balzer
1231:
1205:
1192:
1185:
1159:
1152:
1123:
1087:
1081:978-1492043454
1080:
1063:
1056:
1038:
1017:"What Is SOA?"
1008:
990:
960:
954:978-1492043454
953:
936:
907:
905:
902:
901:
900:
895:
892:
887:
881:
876:
874:SOA governance
871:
866:
861:
859:Loose coupling
856:
849:
846:
840:
837:
836:
835:
832:
829:
826:
823:
820:
813:
779:Main article:
776:
773:
753:
750:
742:Main article:
739:
736:
731:Main article:
728:
725:
723:
720:
719:
718:
712:
709:
706:
661:
658:
641:
640:
637:
634:
606:best practices
586:
583:
503:
502:
497:
492:
487:
481:
476:
471:
465:
458:
455:
399:
396:
378:
377:
373:
370:
358:
355:
347:
339:
336:
335:
334:
331:
325:
322:
317:
314:
309:
306:
301:
298:
295:
292:
287:
284:
279:
276:
271:
268:
263:
259:
256:
253:
250:
247:
244:
237:
225:
224:
190:
188:
181:
175:
172:
143:loose coupling
133:
130:
117:
114:
88:
87:
84:
77:
74:
26:
9:
6:
4:
3:
2:
2977:
2966:
2963:
2961:
2958:
2956:
2953:
2951:
2948:
2946:
2943:
2942:
2940:
2925:
2917:
2915:
2907:
2906:
2903:
2897:
2894:
2892:
2889:
2887:
2884:
2882:
2879:
2877:
2874:
2872:
2869:
2868:
2866:
2862:
2852:
2849:
2847:
2844:
2842:
2839:
2837:
2834:
2833:
2831:
2827:
2821:
2818:
2816:
2815:Systems model
2813:
2811:
2808:
2806:
2803:
2801:
2798:
2796:
2793:
2791:
2788:
2786:
2783:
2781:
2778:
2776:
2773:
2772:
2770:
2766:
2760:
2757:
2755:
2752:
2750:
2747:
2745:
2742:
2740:
2737:
2735:
2732:
2730:
2727:
2725:
2722:
2720:
2717:
2715:
2712:
2710:
2707:
2705:
2702:
2700:
2697:
2695:
2692:
2690:
2687:
2686:
2684:
2682:Developmental
2680:
2677:
2673:
2667:
2664:
2662:
2659:
2657:
2654:
2652:
2649:
2647:
2644:
2642:
2639:
2638:
2636:
2632:
2626:
2623:
2619:
2616:
2615:
2614:
2611:
2609:
2606:
2604:
2601:
2599:
2596:
2594:
2591:
2589:
2586:
2584:
2581:
2579:
2576:
2574:
2571:
2569:
2566:
2564:
2561:
2559:
2556:
2554:
2551:
2549:
2546:
2544:
2543:Data modeling
2541:
2537:
2534:
2532:
2529:
2527:
2524:
2522:
2519:
2517:
2514:
2513:
2512:
2509:
2507:
2504:
2502:
2499:
2498:
2496:
2492:
2486:
2483:
2481:
2478:
2476:
2473:
2471:
2468:
2466:
2463:
2461:
2458:
2456:
2453:
2451:
2448:
2446:
2443:
2441:
2438:
2436:
2433:
2431:
2428:
2426:
2423:
2421:
2418:
2417:
2415:
2411:
2407:
2400:
2395:
2393:
2388:
2386:
2381:
2380:
2377:
2370:
2366:
2351:
2307:September 21,
2299:
2295:
2291:
2287:
2281:
2277:
2273:
2269:
2262:
2257:
2256:
2242:
2238:
2234:
2228:
2223:
2218:
2214:
2210:
2206:
2205:
2200:
2193:
2178:
2174:
2170:
2168:9781450306812
2164:
2160:
2156:
2153:. p. 1.
2152:
2148:
2141:
2126:
2120:
2116:
2112:
2108:
2104:
2097:
2089:
2085:
2081:
2077:
2072:
2071:10044/1/40557
2067:
2063:
2059:
2055:
2051:
2050:IEEE Software
2044:
2037:
2029:
2022:
2013:
2008:
2001:
1985:
1981:
1977:
1973:
1969:
1965:
1961:
1957:
1950:
1948:
1931:
1925:
1914:September 22,
1910:
1906:
1900:
1889:September 22,
1884:
1880:
1876:
1870:
1854:
1850:
1844:
1828:
1822:
1815:
1811:
1807:
1804:
1798:
1791:
1787:
1783:
1780:
1774:
1767:
1763:
1759:
1756:
1750:
1742:
1735:
1719:
1715:
1709:
1703:
1699:
1693:
1686:
1685:Computer User
1680:
1673:
1669:
1665:
1662:
1656:
1649:
1644:
1633:
1626:
1610:
1604:
1593:September 10,
1589:
1588:
1583:
1582:"www.ibm.com"
1577:
1568:
1560:
1556:
1551:
1546:
1542:
1538:
1531:
1524:
1516:
1510:
1506:
1499:
1491:
1485:
1476:
1471:
1467:
1463:
1462:IEEE Software
1459:
1452:
1444:
1440:
1436:
1430:
1426:
1422:
1418:
1414:
1407:
1399:
1395:
1391:
1385:
1381:
1377:
1373:
1369:
1362:
1353:
1349:
1345:
1339:
1335:
1331:
1327:
1320:
1304:
1300:
1294:
1288:
1284:
1278:
1263:
1259:
1252:
1245:
1241:
1235:
1219:
1215:
1209:
1202:
1196:
1188:
1182:
1178:
1173:
1172:
1163:
1155:
1149:
1145:
1140:
1139:
1130:
1128:
1119:
1113:
1102:September 21,
1097:
1091:
1083:
1077:
1073:
1067:
1059:
1053:
1049:
1042:
1031:September 21,
1026:
1022:
1018:
1012:
1004:
1000:
994:
983:September 21,
978:
974:
970:
964:
956:
950:
946:
940:
925:
921:
915:
913:
908:
899:
896:
893:
891:
888:
885:
882:
880:
877:
875:
872:
870:
867:
865:
862:
860:
857:
855:
852:
851:
845:
833:
830:
827:
824:
821:
818:
814:
811:
810:
809:
806:
804:
800:
796:
792:
788:
782:
781:Microservices
775:Microservices
772:
768:
764:
762:
758:
749:
745:
734:
716:
713:
710:
707:
704:
703:
702:
698:
694:
691:
685:
683:
679:
675:
671:
667:
657:
655:
649:
647:
638:
635:
632:
627:
626:
625:
622:
618:
616:
612:
607:
602:
598:
596:
592:
578:
570:
566:
564:
559:
555:
551:
549:
545:
540:
536:
532:
528:
524:
521:
516:
511:
509:
508:interoperable
501:
498:
496:
493:
491:
490:Apache Thrift
488:
485:
482:
480:
477:
475:
472:
469:
466:
463:
459:
456:
454:
450:
447:
446:
445:
442:
440:
436:
432:
428:
424:
420:
416:
411:
409:
408:Microservices
405:
395:
393:
389:
385:
383:
374:
371:
368:
364:
359:
356:
353:
348:
345:
344:
343:
332:
330:
329:encapsulation
326:
323:
321:
318:
315:
313:
310:
307:
305:
302:
299:
296:
293:
291:
288:
285:
283:
280:
277:
275:
272:
269:
267:
264:
260:
257:
254:
251:
248:
245:
242:
238:
236:
233:
232:
231:
221:
212:is available.
211:
207:
201:
200:
196:
191:This article
189:
180:
179:
171:
169:
165:
161:
157:
153:
148:
145:
144:
139:
129:
127:
123:
113:
110:
108:
103:
101:
97:
93:
85:
82:
78:
75:
72:
71:
70:
67:
64:
61:
57:
53:
49:
45:
41:
37:
33:
19:
2965:Web services
2810:Object model
2805:Metamodeling
2734:Spiral model
2660:
2634:Orientations
2305:. Retrieved
2298:the original
2267:
2244:. Retrieved
2203:
2192:
2180:. Retrieved
2150:
2140:
2128:. Retrieved
2106:
2096:
2056:(3): 42–52.
2053:
2049:
2036:
2021:
2012:1606.04036v1
2000:
1990:February 23,
1988:. Retrieved
1984:the original
1966:(3): 36–41.
1963:
1959:
1934:. Retrieved
1924:
1912:. Retrieved
1908:
1899:
1887:. Retrieved
1883:the original
1878:
1869:
1857:. Retrieved
1843:
1831:. Retrieved
1821:
1813:
1797:
1789:
1773:
1765:
1749:
1734:
1722:. Retrieved
1718:the original
1708:
1701:
1692:
1684:
1679:
1672:CIO Magazine
1671:
1655:
1647:
1643:
1625:
1613:. Retrieved
1603:
1591:. Retrieved
1585:
1576:
1567:
1540:
1536:
1523:
1505:SOA Patterns
1504:
1498:
1484:cite journal
1468:(1): 13–19.
1465:
1461:
1451:
1412:
1406:
1367:
1361:
1325:
1319:
1309:September 9,
1307:. Retrieved
1302:
1293:
1277:
1267:September 3,
1265:. Retrieved
1261:
1251:
1243:
1234:
1222:. Retrieved
1218:the original
1208:
1200:
1195:
1170:
1162:
1137:
1100:. Retrieved
1090:
1071:
1066:
1047:
1041:
1029:. Retrieved
1025:the original
1020:
1011:
1002:
993:
981:. Retrieved
977:the original
972:
963:
944:
939:
927:. Retrieved
923:
842:
807:
784:
769:
765:
757:Tim O'Reilly
755:
747:
699:
695:
686:
666:Web services
663:
650:
642:
623:
619:
603:
599:
595:architecture
594:
588:
563:project plan
552:
525:
512:
504:
449:Web services
443:
412:
404:web services
401:
386:
379:
351:
341:
228:
215:
210:Editing help
192:
149:
141:
135:
119:
111:
104:
92:service mesh
89:
68:
65:
58:, through a
39:
35:
29:
2501:Abstraction
2246:February 9,
2182:February 9,
2130:February 9,
1766:XML Journal
690:scalability
2939:Categories
2820:View model
2785:Data model
2365:Audio help
2356:2011-10-27
1687:. Page 20.
1615:August 13,
1283:Thomas Erl
1224:August 13,
904:References
676:(WCF) and
646:idempotent
510:services.
174:Principles
2829:Languages
2080:0740-7459
1545:CiteSeerX
929:March 30,
799:protocols
791:processes
660:Criticism
262:tomorrow.
218:July 2024
140:promotes
81:black box
2924:Category
2790:ER model
2656:Ontology
2568:Software
2494:Concepts
2367: ·
2177:53246415
2088:18802650
1936:June 10,
1909:wso2.com
1859:June 27,
1833:June 27,
1814:devx.com
1806:Archived
1782:Archived
1758:Archived
1743:. ZDNet.
1664:Archived
1398:17957063
1352:13156128
1303:InformIT
1112:cite web
848:See also
715:Platform
561:craft a
529:such as
338:Patterns
327:Service
126:metadata
116:Overview
79:It is a
2914:Commons
2739:V-model
2354: (
2325:minutes
2241:9511734
1980:2859262
1724:May 18,
1443:1837914
795:network
761:Web 2.0
752:Web 2.0
682:VTD-XML
672:(JBI),
631:agility
548:portals
520:Java EE
160:mashups
2675:Models
2425:DevOps
2413:Fields
2294:457705
2292:
2282:
2239:
2229:
2175:
2165:
2121:
2086:
2078:
1978:
1547:
1511:
1441:
1431:
1396:
1386:
1350:
1340:
1183:
1150:
1078:
1054:
951:
803:DevOps
654:JSR-89
535:WS-CDL
500:SORCER
474:OPC-UA
193:is in
166:, and
2851:SysML
2775:SPICE
2768:Other
2729:Scrum
2689:Agile
2641:Agile
2625:CI/CD
2301:(PDF)
2290:S2CID
2264:(PDF)
2237:S2CID
2173:S2CID
2084:S2CID
2046:(PDF)
2007:arXiv
1976:S2CID
1853:ZDNet
1635:(PDF)
1533:(PDF)
1439:S2CID
1394:S2CID
1348:S2CID
886:(SOC)
615:CORBA
589:Some
470:(DDS)
437:, or
427:CORBA
199:prose
2836:IDEF
2780:CMMI
2666:SDLC
2309:2021
2280:ISBN
2248:2021
2227:ISBN
2184:2021
2163:ISBN
2132:2021
2119:ISBN
2076:ISSN
1992:2008
1938:2008
1916:2016
1891:2016
1861:2009
1835:2009
1726:2024
1617:2012
1595:2016
1509:ISBN
1490:link
1429:ISBN
1417:IEEE
1384:ISBN
1372:IEEE
1356:2004
1338:ISBN
1311:2021
1269:2012
1226:2012
1181:ISBN
1148:ISBN
1118:link
1104:2016
1076:ISBN
1052:ISBN
1033:2016
985:2016
949:ISBN
931:2021
537:and
531:BPEL
495:gRPC
453:SOAP
439:gRPC
435:REST
423:Jini
415:SOAP
363:UDDI
350:more
195:list
164:SaaS
154:and
122:pass
2846:USL
2841:UML
2719:RAD
2694:EUP
2272:doi
2217:hdl
2209:doi
2155:doi
2111:doi
2066:hdl
2058:doi
1968:doi
1587:IBM
1555:doi
1470:doi
1421:doi
1376:doi
1330:doi
1244:IBM
1177:390
546:or
484:WCF
406:or
40:SOA
30:In
2941::
2749:XP
2724:UP
2323:54
2288:.
2278:.
2266:.
2235:.
2225:.
2215:.
2201:.
2171:.
2161:.
2149:.
2117:.
2105:.
2082:.
2074:.
2064:.
2054:33
2052:.
2048:.
1974:.
1962:.
1958:.
1946:^
1907:.
1877:.
1851:.
1812:.
1788:.
1764:.
1700:,
1670:,
1584:.
1553:.
1541:30
1539:.
1535:.
1486:}}
1482:{{
1466:33
1464:.
1460:.
1437:.
1427:.
1415:.
1392:.
1382:.
1370:.
1346:.
1336:.
1301:.
1260:.
1242:,
1179:.
1146:.
1126:^
1114:}}
1110:{{
1019:.
1001:.
971:.
922:.
911:^
819:),
617:.
550:.
441:.
433:,
429:,
425:,
162:,
34:,
2398:e
2391:t
2384:v
2371:)
2363:(
2358:)
2327:)
2320:(
2311:.
2274::
2250:.
2219::
2211::
2186:.
2157::
2134:.
2113::
2090:.
2068::
2060::
2030:.
2015:.
2009::
1994:.
1970::
1964:9
1940:.
1918:.
1893:.
1863:.
1837:.
1816:.
1792:.
1768:.
1728:.
1637:.
1619:.
1597:.
1561:.
1557::
1517:.
1492:)
1478:.
1472::
1445:.
1423::
1400:.
1378::
1354:.
1332::
1313:.
1271:.
1228:.
1189:.
1156:.
1144:3
1120:)
1106:.
1084:.
1060:.
1035:.
1005:.
987:.
957:.
933:.
369:.
352:.
220:)
216:(
202:.
38:(
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.