Blog‎ > ‎

Finished reading Service oriented Architecture (SoA) book

posted Sep 17, 2014, 8:30 AM by Sami Lehtinen   [ updated Sep 17, 2014, 8:30 AM ]
Finished reading: Service-oriented architecture (SOA) book

Compact keyword list:
software design and software architecture design pattern, providing application functionality, service-orientation, vendor, product or technology, independent, software applications, Design concept, Web Services Description Language (WSDL), SOAP (originally Simple Object Access Protocol), metadata, catalogue, autodiscovery, reasonable expenditure of cost and effort. Granularity of services, processing overhead, easy reuse. Access independent services without knowledge of the service's platform implementation. Business Process Layer, Services, Service Components, Operational Systems. Layers: Consumer Interface Layer, Integration Layer, Quality of Service, Informational, Governance, each service is built as a discrete piece of code. Design principles,deploy SOA services in different implementation languages; well-defined interface, integrate widely disparate applications, well-defined, shared format, concepts of distributed computing and modular programming, promoting reuse. SaaS, and cloud computing service-description documents. Service loose coupling. Minimizes dependencies, Service abstraction, Service reusability, promoting reuse. Service autonomy, Service statelessness, Service discoverability, Service composability, Service granularity, Service normalization, Service optimization, Service encapsulation, Location transparency, Service-orientation design paradigm, composition-centric. Service composition, Service Abstraction, service inventory. Blueprint, Service-oriented enterprise architecture, technological resources, wrappers around existing legacy systems to make them network-enabled. Service provider, trade-offs between security and easy availability, Universal Description Discovery and Integration (UDDI), ebXML (Electronic Business using eXtensible Markup Language), ISO/IEC 11179 Metadata Registry (MDR), Service consumer, Service-Oriented Modeling Framework (SOMF). Independent of the underlying platform and programming language. The interface definition hides the implementation of the language-specific service. SOA-based systems can therefore function independently of development technologies and platforms. Wrap COBOL legacy systems and present them as software services. This has extended the useful life of many core legacy systems indefinitely, no matter what language they originally used. Service Object-Oriented Architecture (SOOA), Service Protocol Oriented Architecture (SPOA), Service interfaces, Communication protocol, Bind operation. Service concept, Business services, Service development scheme. Project plan, OASIS defines SOA as the following: A paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. It provides a uniform means to offer, discover, interact with and use capabilities to produce desired effects consistent with measurable preconditions and expectations. Business-oriented infrastructure. Well-defined, highly inter-operable interfaces. Maximize reuse of services. Stand-alone unit of functionality, formally defined interface. The coordinated work of subordinate services. Abstraction Autonomy Composability Discoverability Formal contract Loose coupling Reusability Statelessness, tested as a 'black box'. Out-of-scope services, regression test documentation, SOA Governance, horizontal trust, business Motivation Model (BMM). Security models, application-managed security, change management governance, shortage of skilled people, services infrastructure. Interoperability SOA implementations. Developed basic profile (BP) and basic security profile (BSP) to enforce compatibility. Services conform to WS-I profile guidelines. Reliable Secure Profile. Exaggerated expectations. System architecture and design. Do a poor job of introducing SOA concepts to a business with the result that SOA remains misunderstood within that business. Appropriate support structure, service-level obligations, Business units, Corporate incentives, SaaS monetization architecture. Require more processing power, increasing costs. Overheads, Scalability, Shared context, Transaction, Security, Contingency for additional proof-of-concept work. A service delivery platform (SDP), business information models, identity management, products, content, devices, and the end-user service characteristics, agile, vendor community, Business value over technical strategy Strategic goals over project-specific benefits Intrinsic interoperability over custom integration Shared services over specific-purpose implementations Flexibility over optimization Evolutionary refinement over pursuit of initial perfection. Web 2.0, RESTful web APIs, mashups, integrated user experience, service-oriented business applications (SOBAs). Philosophy of encapsulating application logic in services, defined interface, publicly available, discovery mechanisms. Complexity-hiding, technologies used in real-world applications. Use-cases demonstrated the potential of combining technologies and principles of both Web 2.0 and SOA. "Internet of Services", novel business models, and approaches, digital nervous system, Zero Latency Enterprise.

Yep, this isn't my own text. This is just compact keyword dump about the stuff I've been reading lately.