Software Life-Cycle Management
|
|
- Nelson Gordon
- 8 years ago
- Views:
Transcription
1 Ingo Arnold Department Computer Science University of Basel Theory Software Life-Cycle Management Architecture Styles
2 Overview An Architecture Style expresses a fundamental structural organization schema for software systems An Architectural Style provides a set of predefined element types specifies their responsibilities includes rules and guidelines for organizing the relationships between them There is some overlap between Architecture Styles and Patterns Department of Computer Sciences University of Basel 2
3 Benefits Architecture Styles similar to Patterns are A store of knowledge - Patterns are a store of knowledge about solving a particular type of problem in a particular domain - Documenting this knowledge allows it to be shared among people solving similar problems - People can move between specialist areas more easily and work more effectively within a particular area by sharing knowledge about success and failure Examples of good practices. - A set of patterns provides examples of good design practices - You can use these examples directly and re-apply them within your given context A language - Patterns allow designers to create and share a common language for discussing design problems - This common language helps designers relate ideas to each other easily and analyze alternative solutions to a problem - This allows for more effective communication among participants in the design process Department of Computer Sciences University of Basel 3
4 Benefits Architecture Styles similar to Patterns are An aid to standardization - The use of patterns encourages designers to choose standard solutions to recurring problems rather than searching for novel solutions in each case - This has obvious efficiency benefits for the design process, and reliability is also likely to increase because of the reuse that results from the application of an already proven solution Encouragement of generality - Good patterns are usually generic, flexible, and reusable in a number of situations - Providing flexible and generic solutions to problems is often a goal for architects as well - Using patterns as inputs to the design process and thinking in terms of identifying design patterns within the design process can help you create flexible, generic solutions to the problems within your system Department of Computer Sciences University of Basel 4
5 Pipes & Filters Architecture Style Pipes and Filters The Pipes and Filters style is characterized by a single, simple element type (the filter) that processes a data stream, with instances of this type connected by simple connectors known as pipes Example of Use. A few examples follow Advantages. The style allows filter implementation to easily be changed without affecting other system elements, and it makes creating new pipelines by recombining existing filters easy. Parallel processing can also be supported with multiple filters running concurrently Disadvantages. Sharing state information is difficult with this style, and the data transformation required for a common interfilter data format adds overhead. Error handling is difficult and needs to be implemented consistently down the pipeline Common Variants. Pipes can execute in parallel rather than in sequence, or filters can have more than one entrance or exit channel. Department of Computer Sciences University of Basel 5
6 Pipes & Filters Architecture Style Pipes and Filters (continued) In Unix System the Pipes and Filters style is the pre-dominant model for Shell programming Department of Computer Sciences University of Basel 6
7 Pipes & Filters Architecture Style Pipes and Filters (continued) In Unix System the Pipes and Filters style is the pre-dominant model for Shell programming Department of Computer Sciences University of Basel 7
8 Pipes & Filters Architecture Style Pipes and Filters (continued) The Chain of Responsibility Pattern conceptually outlines the static model this style is based upon Department of Computer Sciences University of Basel 8
9 Pipes & Filters Architecture Style Pipes and Filters (continued) Also Workflow Systems are often using this pattern as their underlying organisation schema Department of Computer Sciences University of Basel 9
10 Pipes & Filters Architecture Style Pipes and Filters (continued) Also Workflow Systems are often using this pattern as their underlying organisation schema Department of Computer Sciences University of Basel 10
11 Pipes & Filters Architecture Style Pipes and Filters (continued) Also Workflow Systems are often using this pattern as their underlying organisation schema Department of Computer Sciences University of Basel 11
12 Pipes & Filters Architecture Style Pipes and Filters (continued) Also EAI or ESB types of Systems use Pipes and Filters as their internal means of abstracting - Processing nodes (Filters) - Connectors between these (Pipes) Department of Computer Sciences University of Basel 12
13 Client / Server Architecture Style Client / Server This very widely used style defines a system structure comprised of two types of elements - A server that provides one or more services via a well-defined interface - A client that uses the services as part of its operation The client and server are typically assumed to reside on different machines in a network (although this is not a requirement) Example of Use. This style is probably very familiar to you from mainstream IT technologies such as client/server databases Advantages. The advantages of the style include the centralization of complex or sensitive processing Disadvantages. Making the request and receiving the response between clients and servers that do not reside on the same machine introduces some unavoidable inefficiency Common Variants. - Stateful Server (where the server is responsible for tracking of conversational state) - Stateful Client, Stateless Server (where the client is responsible for conv. state) Department of Computer Sciences University of Basel 13
14 Client / Server Architecture Style Client / Server (continued) Department of Computer Sciences University of Basel 14
15 Tiered Computing Architecture Style Tiered Computing A development of the Client/Server style The Tiered Computing style is widely used in enterprise information systems A tiered system is considered to contain a number of tiers of computation, which combine to offer a service to an ultimate consumer (e.g., a human user) Each tier acts as a server for its caller and as a client to the next tier in the architecture A key architectural principle is that a tier can communicate in this way only with the tiers immediately on either side of it a tier is not aware of the existence of other tiers in the system apart from its neighbors Common tiers in enterprise information systems include the following - Client - Presentation - Business Logic - Integration - Database & Persistence Systems Department of Computer Sciences University of Basel 15
16 Tiered Computing Architecture Style Tiered Computing (continued) Example of Use. Most large enterprise information systems are organized into tiers, and a number of common application development technologies (such as J2EE and.net) encourage this organization Advantages. This style allows a clear separation of concerns between tiers and provides the potential for reusability of the simpler tiers (data storage, data access, and business transactions) across a number of systems Disadvantages. Disadvantages of the style include the overhead of communication between the tiers and additional development complexity arising from the number of system elements that need to be developed and integrated across the tiers Department of Computer Sciences University of Basel 16
17 Tiered Computing Architecture Style Tiered Computing (continued) Department of Computer Sciences University of Basel 17
18 Peer-to-Peer Architecture Style Peer-to-Peer Often referred to as P2P, this architectural style defines - a single type of system element (the peer) - a single type of connector that is a network connection (an interpeer connection) The characteristics of the connector are not important to the style, and the style has been used with a number of types of network connections The central organizational principle of the system is that any peer is free to communicate directly with any other peer, without needing to use a central server Peers typically locate each other by automatically exchanging lists of known peers Each peer is capable of acting as both client (when making requests) and server (when servicing requests), often being both concurrently. Department of Computer Sciences University of Basel 18
19 Peer-to-Peer Architecture Style Peer-to-Peer (continued) Example of Use. Well-known examples of the P2P style include Internet fileswapping applications and distributed computation systems Advantages. P2P systems eliminate the possible point of failure that a central server represents, can be made very scalable, and are resilient to partial failures in the underlying network Disadvantages. Disadvantages of P2P systems include the possible partitioning of the network if no central peer list is available and the difficulty of guaranteeing a particular response from the system at any point in time Department of Computer Sciences University of Basel 19
20 Peer-to-Peer Architecture Style Peer-to-Peer (continued) Department of Computer Sciences University of Basel 20
21 Layered Implementation Architecture Style Layered Implementation The Layered Implementation style identifies a single type of system element - the layer The style organizes a system's implementation into a stack of layers, with each layer providing a service to the layer above it and requesting services from the one below it The layers are ordered by the level of abstraction they represent, with the most abstract (e.g., organization-specific operations) at the top of the stack and the least abstract (e.g., operating system specific libraries) at the bottom Depending on the implementation of the style, a layer may be able to communicate directly with any of the layers below it (relaxed layering) or only with the layer directly below it (strict layering) Department of Computer Sciences University of Basel 21
22 Layered Implementation Architecture Style Layered Implementation (continued) Example of Use. Communication stacks are the classic example of layered organization, but most information system technologies are organized in this way too (e.g., a locally developed utility library layered above a third-party library layered above the operating system) Advantages. Likely advantages of this style of organization include the reuse of layers, good separation of concerns, and relatively easy maintenance due to the isolation of each layer's implementation Disadvantages. Disadvantages include a reduction in implementation flexibility, a reduction in efficiency when many layers need to be traversed, and the constraints that the style places on the development process (layers often need to be developed in order) Department of Computer Sciences University of Basel 22
23 Layered Implementation Architecture Style Layered Implementation (continued) Department of Computer Sciences University of Basel 23
24 Layered Implementation Architecture Style Layered Implementation (continued) Layers can be contrasted with the tiers in the Tiered Computing style because layers are organized based on the level of abstraction they deal with, whereas tiers are organized based on the type of service they provide All of the layers in a particular implementation are concerned with providing a single service, but each layer is concerned with a different level of abstraction involved in providing the service In contrast, the tiers in an implementation all operate at a broadly similar level of abstraction but are each concerned with providing a different type of service, which, when the services are combined, creates a useful system Given this difference, tiers are often visualized as running horizontally, while layers are often visualized as running vertically Indeed, the two styles are often combined, with each tier in the system using a stack of layers within it to organize its implementation into different levels of abstraction Department of Computer Sciences University of Basel 24
25 Layered Implementation Architecture Style Layered Implementation (continued) Department of Computer Sciences University of Basel 25
26 Publisher/Subscriber Architecture Style Publisher/Subscriber The Publisher/Subscriber style grew out of a realization that client/server interactions are not suitable for all types of distributed system problems The style defines - a single system element (the publisher) that creates information of interest to - any number of system elements (the subscribers) that may wish to consume it A single type of connector, a reliable network link, is used to link the publisher and the subscribers The subscribers register their interest in certain information with the publisher When the publisher creates or changes information that subscribers have registered their interest in, the publisher notifies the relevant subscribers of the change Depending on the implementation of the style, the notification may contain the new or changed information, or it may just be a notification of a relevant change, leaving the subscribers to query the publisher for changes themselves Department of Computer Sciences University of Basel 26
27 Publisher/Subscriber Architecture Style Publisher/Subscriber (continued) Example of Use. The Publisher/Subscriber style is widely implemented in enterprise messaging systems Advantages. Advantages include the flexibility to add new subscribers dynamically, the relatively loose coupling between publisher and subscribers, and the increased efficiency that comes from the subscribers not having to poll the publisher repeatedly to find new and changed information Disadvantages. The main disadvantage of the style is its relatively complex implementation (particularly if reliable delivery of messages is required) Department of Computer Sciences University of Basel 27
28 Publisher/Subscriber Architecture Style Publisher/Subscriber (continued) Department of Computer Sciences University of Basel 28
29 Asynchronous Data Replication Architecture Style Asynchronous Data Replication Asynchronous Data Replication, is a style used where information in two data stores needs to be kept synchronized The style has three element types - Data source. A data store that owns a particular type of information - Data replica. Separate data store that wishes to maintain a synchronized copy of some subset of the information in the source - Replicator. Element responsible for recognizing changes or additions to information in the source and performing the synchronization of the replica data store Department of Computer Sciences University of Basel 29
30 Asynchronous Data Replication Architecture Style Asynchronous Data Replication (continued) Example of Use. This style is widely implemented in enterprise data replication technologies, such as those supplied by the major database vendors Advantages. The advantages of the style include the ability to synchronize two data stores automatically and efficiently, without needing to complicate the application logic Disadvantages. Common problems include the latency that can occur between source update and replica update as well as the complexity of dealing with updates at the replica data store Department of Computer Sciences University of Basel 30
31 Asynchronous Data Replication Architecture Style Asynchronous Data Replication (continued) Department of Computer Sciences University of Basel 31
32 Integration Hub Architecture Style Integration Hub The Integration Hub style is another data-oriented architectural style, extending Asynchronous Data Replication to situations where information needs to be synchronized between a number of different systems (rather than between replica data stores) This style defines four types of system elements - Data source - Data destination - Hub - Adapter The elements are organized into a cartwheel form, with the hub at the center of the wheel and the data sources and destinations at the outer edges of the spokes Along every spoke, between hub and source or destination is an adapter (so each spoke is an adapter connected to a source or destination, radiating out from the hub) Department of Computer Sciences University of Basel 32
33 Integration Hub Architecture Style Integration Hub (continued) Example of Use. This style is widely implemented by EAI products that allow data integration between applications Advantages. Integration Hub allows new data sources and destinations to be added easily to the system without disrupting the existing implementation. It can also integrate sources and destinations of practically any form because a dedicated adapter hides the specifics of a source or destination Disadvantages. - Data movement between applications will be relatively inefficient due to the amount of translation, and the imposition of a common model may mean that some information that the common model does not accommodate is lost in translation - The design of the common model can also be quite difficult - The hub itself can become a central point of failure or a performance bottleneck if it is not designed properly - This risk can be mitigated to some extent by extending the cartwheel topology into a snowflake which links multiple hubs together Department of Computer Sciences University of Basel 33
34 Integration Hub Architecture Style Integration Hub (continued) Department of Computer Sciences University of Basel 34
35 Questions? Department of Computer Sciences University of Basel 35
Enterprise Application Integration (EAI) Architectures, Technologies, and Best Practices
Enterprise Application Integration (EAI) Architectures, Technologies, and Best Practices Give Your Business the Competitive Edge IT managers have been under increasing pressure to migrate a portfolio of
More informationAdvanced Analysis and Design
Advanced Analysis and Design Architectural Styles Professor David S. Rosenblum Department of Computer Science http://www.cs.ucl.ac.uk/staff/d.rosenblum/ Architectural Styles A set of design rules that
More informationIkasan ESB Reference Architecture Review
Ikasan ESB Reference Architecture Review EXECUTIVE SUMMARY This paper reviews the Ikasan Enterprise Integration Platform within the construct of a typical ESB Reference Architecture model showing Ikasan
More informationPatterns in Software Engineering
Patterns in Software Engineering Lecturer: Raman Ramsin Lecture 7 GoV Patterns Architectural Part 1 1 GoV Patterns for Software Architecture According to Buschmann et al.: A pattern for software architecture
More informationObjectives. Distributed Databases and Client/Server Architecture. Distributed Database. Data Fragmentation
Objectives Distributed Databases and Client/Server Architecture IT354 @ Peter Lo 2005 1 Understand the advantages and disadvantages of distributed databases Know the design issues involved in distributed
More informationKnowledgent White Paper Series. Developing an MDM Strategy WHITE PAPER. Key Components for Success
Developing an MDM Strategy Key Components for Success WHITE PAPER Table of Contents Introduction... 2 Process Considerations... 3 Architecture Considerations... 5 Conclusion... 9 About Knowledgent... 10
More informationSERVICE-ORIENTED MODELING FRAMEWORK (SOMF ) SERVICE-ORIENTED SOFTWARE ARCHITECTURE MODEL LANGUAGE SPECIFICATIONS
SERVICE-ORIENTED MODELING FRAMEWORK (SOMF ) VERSION 2.1 SERVICE-ORIENTED SOFTWARE ARCHITECTURE MODEL LANGUAGE SPECIFICATIONS 1 TABLE OF CONTENTS INTRODUCTION... 3 About The Service-Oriented Modeling Framework
More informationchapater 7 : Distributed Database Management Systems
chapater 7 : Distributed Database Management Systems Distributed Database Management System When an organization is geographically dispersed, it may choose to store its databases on a central database
More informationCHAPTER 2 MODELLING FOR DISTRIBUTED NETWORK SYSTEMS: THE CLIENT- SERVER MODEL
CHAPTER 2 MODELLING FOR DISTRIBUTED NETWORK SYSTEMS: THE CLIENT- SERVER MODEL This chapter is to introduce the client-server model and its role in the development of distributed network systems. The chapter
More informationIT Architecture Review. ISACA Conference Fall 2003
IT Architecture Review ISACA Conference Fall 2003 Table of Contents Introduction Business Drivers Overview of Tiered Architecture IT Architecture Review Why review IT architecture How to conduct IT architecture
More informationArchitecture Design & Sequence Diagram. Week 7
Architecture Design & Sequence Diagram Week 7 Announcement Reminder Midterm I: 1:00 1:50 pm Wednesday 23 rd March Ch. 1, 2, 3 and 26.5 Hour 1, 6, 7 and 19 (pp.331 335) Multiple choice Agenda (Lecture)
More informationSTRATEGIES ON SOFTWARE INTEGRATION
STRATEGIES ON SOFTWARE INTEGRATION Cornelia Paulina Botezatu and George Căruţaşu Faculty of Computer Science for Business Management Romanian-American University, Bucharest, Romania ABSTRACT The strategy
More informationComparing Microsoft SQL Server 2005 Replication and DataXtend Remote Edition for Mobile and Distributed Applications
Comparing Microsoft SQL Server 2005 Replication and DataXtend Remote Edition for Mobile and Distributed Applications White Paper Table of Contents Overview...3 Replication Types Supported...3 Set-up &
More informationPrinciples and Foundations of Web Services: An Holistic View (Technologies, Business Drivers, Models, Architectures and Standards)
Principles and Foundations of Web Services: An Holistic View (Technologies, Business Drivers, Models, Architectures and Standards) Michael P. Papazoglou (INFOLAB/CRISM, Tilburg University, The Netherlands)
More informationService Oriented Architecture
Service Oriented Architecture Version 9 2 SOA-2 Overview Ok, now we understand the Web Service technology, but how about Service Oriented Architectures? A guiding analogy Terminology excursion Service,
More informationBuilding Hyper-Scale Platform-as-a-Service Microservices with Microsoft Azure. Patriek van Dorp and Alex Thissen
Building Hyper-Scale Platform-as-a-Service Microservices with Microsoft Azure Patriek van Dorp and Alex Thissen About me: Patriek van Dorp pvandorp@xpirit.com @pvandorp Xpirit http://onwindowsazure.com
More informationSoftware Engineering
Software Engineering Lecture 06: Design an Overview Peter Thiemann University of Freiburg, Germany SS 2013 Peter Thiemann (Univ. Freiburg) Software Engineering SWT 1 / 35 The Design Phase Programming in
More informationSOFT 437. Software Performance Analysis. Ch 5:Web Applications and Other Distributed Systems
SOFT 437 Software Performance Analysis Ch 5:Web Applications and Other Distributed Systems Outline Overview of Web applications, distributed object technologies, and the important considerations for SPE
More informationInformation Systems Analysis and Design CSC340. 2004 John Mylopoulos. Software Architectures -- 1. Information Systems Analysis and Design CSC340
XIX. Software Architectures Software Architectures UML Packages Client- vs Peer-to-Peer Horizontal Layers and Vertical Partitions 3-Tier and 4-Tier Architectures The Model-View-Controller Architecture
More informationStock Trader System. Architecture Description
Stock Trader System Architecture Description Michael Stevens mike@mestevens.com http://www.mestevens.com Table of Contents 1. Purpose of Document 2 2. System Synopsis 2 3. Current Situation and Environment
More informationARCHITECTURAL DESIGN OF MODERN WEB APPLICATIONS
ARCHITECTURAL DESIGN OF MODERN WEB APPLICATIONS Lech MADEYSKI *, Michał STOCHMIAŁEK Abstract. Architectural design is about decisions which influence characteristics of arising system e.g. maintainability
More informationSOA REFERENCE ARCHITECTURE: WEB TIER
SOA REFERENCE ARCHITECTURE: WEB TIER SOA Blueprint A structured blog by Yogish Pai Web Application Tier The primary requirement for this tier is that all the business systems and solutions be accessible
More informationDistributed Data Management
Introduction Distributed Data Management Involves the distribution of data and work among more than one machine in the network. Distributed computing is more broad than canonical client/server, in that
More informationArchitecting for the cloud designing for scalability in cloud-based applications
An AppDynamics Business White Paper Architecting for the cloud designing for scalability in cloud-based applications The biggest difference between cloud-based applications and the applications running
More informationDefinition of SOA. Capgemini University Technology Services School. 2006 Capgemini - All rights reserved November 2006 SOA for Software Architects/ 2
Gastcollege BPM Definition of SOA Services architecture is a specific approach of organizing the business and its IT support to reduce cost, deliver faster & better and leverage the value of IT. November
More informationClassic Grid Architecture
Peer-to to-peer Grids Classic Grid Architecture Resources Database Database Netsolve Collaboration Composition Content Access Computing Security Middle Tier Brokers Service Providers Middle Tier becomes
More informationTechniques for Scaling Components of Web Application
, March 12-14, 2014, Hong Kong Techniques for Scaling Components of Web Application Ademola Adenubi, Olanrewaju Lewis, Bolanle Abimbola Abstract Every organisation is exploring the enormous benefits of
More informationAn Overview of Distributed Databases
International Journal of Information and Computation Technology. ISSN 0974-2239 Volume 4, Number 2 (2014), pp. 207-214 International Research Publications House http://www. irphouse.com /ijict.htm An Overview
More informationDistributed Systems Architectures
Software Engineering Distributed Systems Architectures Based on Software Engineering, 7 th Edition by Ian Sommerville Objectives To explain the advantages and disadvantages of different distributed systems
More informationCloud Computing and Advanced Relationship Analytics
Cloud Computing and Advanced Relationship Analytics Using Objectivity/DB to Discover the Relationships in your Data By Brian Clark Vice President, Product Management Objectivity, Inc. 408 992 7136 brian.clark@objectivity.com
More informationPatterns of Information Management
PATTERNS OF MANAGEMENT Patterns of Information Management Making the right choices for your organization s information Summary of Patterns Mandy Chessell and Harald Smith Copyright 2011, 2012 by Mandy
More informationSoftware-Defined Networks Powered by VellOS
WHITE PAPER Software-Defined Networks Powered by VellOS Agile, Flexible Networking for Distributed Applications Vello s SDN enables a low-latency, programmable solution resulting in a faster and more flexible
More informationCLOUD BASED SEMANTIC EVENT PROCESSING FOR
CLOUD BASED SEMANTIC EVENT PROCESSING FOR MONITORING AND MANAGEMENT OF SUPPLY CHAINS A VLTN White Paper Dr. Bill Karakostas Bill.karakostas@vltn.be Executive Summary Supply chain visibility is essential
More informationWeb Application Architectures
Web Engineering Web Application Architectures Copyright 2013 Ioan Toma & Srdjan Komazec 1 Where we are? # Date Title 1 5 th March Web Engineering Introduction and Overview 2 12 th March Requirements Engineering
More informationArchitecture. Reda Bendraou reda.bendraou{{@}}lip6.fr http://pagesperso-systeme.lip6.fr/reda.bendraou/
Architecture Reda Bendraou reda.bendraou{{@}}lip6.fr http://pagesperso-systeme.lip6.fr/reda.bendraou/ Some slides were adapted from L. Osterweil, B. Meyer, and P. Müller material Reda Bendraou LI386-S1
More informationMAX DOLGICER EAI (ENTERPRISE APPLICATION INTEGRATION) OCTOBER 11-13, 2006 VISCONTI PALACE HOTEL - VIA FEDERICO CESI, 37 ROME (ITALY)
TECHNOLOGY TRANSFER PRESENTS MAX DOLGICER EAI (ENTERPRISE APPLICATION INTEGRATION) Architectures, Technologies and Best Practices OCTOBER 11-13, 2006 VISCONTI PALACE HOTEL - VIA FEDERICO CESI, 37 ROME
More informationEnterprise Service Bus Defined. Wikipedia says (07/19/06)
Enterprise Service Bus Defined CIS Department Professor Duane Truex III Wikipedia says (07/19/06) In computing, an enterprise service bus refers to a software architecture construct, implemented by technologies
More informationEnterprise Application Designs In Relation to ERP and SOA
Enterprise Application Designs In Relation to ERP and SOA DESIGNING ENTERPRICE APPLICATIONS HASITH D. YAGGAHAVITA 20 th MAY 2009 Table of Content 1 Introduction... 3 2 Patterns for Service Integration...
More informationService Oriented Architecture (SOA) An Introduction
Oriented Architecture (SOA) An Introduction Application Evolution Time Oriented Applications Monolithic Applications Mainframe Client / Server Distributed Applications DCE/RPC CORBA DCOM EJB s Messages
More informationApplying 4+1 View Architecture with UML 2. White Paper
Applying 4+1 View Architecture with UML 2 White Paper Copyright 2007 FCGSS, all rights reserved. www.fcgss.com Introduction Unified Modeling Language (UML) has been available since 1997, and UML 2 was
More informationMANAGING USER DATA IN A DIGITAL WORLD
MANAGING USER DATA IN A DIGITAL WORLD AIRLINE INDUSTRY CHALLENGES AND SOLUTIONS WHITE PAPER OVERVIEW AND DRIVERS In today's digital economy, enterprises are exploring ways to differentiate themselves from
More informationEvent based Enterprise Service Bus (ESB)
Event based Enterprise Service Bus (ESB) By: Kasun Indrasiri 128213m Supervised By: Dr. Srinath Perera Dr. Sanjiva Weerawarna Abstract With the increasing adaptation of Service Oriented Architecture for
More informationDistributed Databases
Distributed Databases Chapter 1: Introduction Johann Gamper Syllabus Data Independence and Distributed Data Processing Definition of Distributed databases Promises of Distributed Databases Technical Problems
More informationData Vault and The Truth about the Enterprise Data Warehouse
Data Vault and The Truth about the Enterprise Data Warehouse Roelant Vos 04-05-2012 Brisbane, Australia Introduction More often than not, when discussion about data modeling and information architecture
More informationA distributed system is defined as
A distributed system is defined as A collection of independent computers that appears to its users as a single coherent system CS550: Advanced Operating Systems 2 Resource sharing Openness Concurrency
More informationCustomer Bank Account Management System Technical Specification Document
Customer Bank Account Management System Technical Specification Document Technical Specification Document Page 1 of 15 Table of Contents Contents 1 Introduction 3 2 Design Overview 4 3 Topology Diagram.6
More informationA standards-based approach to application integration
A standards-based approach to application integration An introduction to IBM s WebSphere ESB product Jim MacNair Senior Consulting IT Specialist Macnair@us.ibm.com Copyright IBM Corporation 2005. All rights
More informationPrinciples of Distributed Database Systems
M. Tamer Özsu Patrick Valduriez Principles of Distributed Database Systems Third Edition
More informationEnterprise Application Integration (EAI) Architectures, Technologies, and Best Practices
Enterprise Application Integration (EAI) Architectures, Technologies, and Best Practices Give Your Business the Competitive Edge IT managers have been under increasing pressure to migrate a portfolio of
More informationComplementing Your Web Services Strategy with Verastream Host Integrator
Verastream Complementing Your Web Services Strategy with Verastream Host Integrator Complementing Your Web Services Strategy with Verastream Host Integrator Complementing Your Web Services Strategy with
More informationService Oriented Architecture 1 COMPILED BY BJ
Service Oriented Architecture 1 COMPILED BY BJ CHAPTER 9 Service Oriented architecture(soa) Defining SOA. Business value of SOA SOA characteristics. Concept of a service, Enterprise Service Bus (ESB) SOA
More informationMotivation Definitions EAI Architectures Elements Integration Technologies. Part I. EAI: Foundations, Concepts, and Architectures
Part I EAI: Foundations, Concepts, and Architectures 5 Example: Mail-order Company Mail order Company IS Invoicing Windows, standard software IS Order Processing Linux, C++, Oracle IS Accounts Receivable
More informationInternational Journal of Scientific & Engineering Research, Volume 4, Issue 11, November-2013 349 ISSN 2229-5518
International Journal of Scientific & Engineering Research, Volume 4, Issue 11, November-2013 349 Load Balancing Heterogeneous Request in DHT-based P2P Systems Mrs. Yogita A. Dalvi Dr. R. Shankar Mr. Atesh
More informationDependability in Web Services
Dependability in Web Services Christian Mikalsen chrismi@ifi.uio.no INF5360, Spring 2008 1 Agenda Introduction to Web Services. Extensible Web Services Architecture for Notification in Large- Scale Systems.
More informationChapter 2 TOPOLOGY SELECTION. SYS-ED/ Computer Education Techniques, Inc.
Chapter 2 TOPOLOGY SELECTION SYS-ED/ Computer Education Techniques, Inc. Objectives You will learn: Topology selection criteria. Perform a comparison of topology selection criteria. WebSphere component
More informationArchitectural patterns
Open Learning Universiteit Unit 3 Learning Unit 3 Architectural patterns Contents Introduction............................................... 35 3.1 Patterns..............................................
More informationATHABASCA UNIVERSITY. Enterprise Integration with Messaging
ATHABASCA UNIVERSITY Enterprise Integration with Messaging BY Anuruthan Thayaparan A thesis essay submitted in partial fulfillment of the requirements for the degree of MASTER OF SCIENCE in INFORMATION
More informationAerospace Software Engineering
16.35 Aerospace Software Engineering Software Architecture The 4+1 view Patterns Prof. Kristina Lundqvist Dept. of Aero/Astro, MIT Why Care About Software Architecture? An architecture provides a vehicle
More informationLuncheon Webinar Series May 13, 2013
Luncheon Webinar Series May 13, 2013 InfoSphere DataStage is Big Data Integration Sponsored By: Presented by : Tony Curcio, InfoSphere Product Management 0 InfoSphere DataStage is Big Data Integration
More informationHow To Build A Financial Messaging And Enterprise Service Bus (Esb)
Simplifying SWIFT Connectivity Introduction to Financial Messaging Services Bus A White Paper by Microsoft and SAGA Version 1.0 August 2009 Applies to: Financial Services Architecture BizTalk Server BizTalk
More informationMS-50401 - Designing and Optimizing Database Solutions with Microsoft SQL Server 2008
MS-50401 - Designing and Optimizing Database Solutions with Microsoft SQL Server 2008 Table of Contents Introduction Audience At Completion Prerequisites Microsoft Certified Professional Exams Student
More informationArchitectural Patterns: From Mud to Structure
DCC / ICEx / UFMG Architectural Patterns: From Mud to Structure Eduardo Figueiredo http://www.dcc.ufmg.br/~figueiredo From Mud to Structure Layered Architecture It helps to structure applications that
More information3-Tier Architecture. 3-Tier Architecture. Prepared By. Channu Kambalyal. Page 1 of 19
3-Tier Architecture Prepared By Channu Kambalyal Page 1 of 19 Table of Contents 1.0 Traditional Host Systems... 3 2.0 Distributed Systems... 4 3.0 Client/Server Model... 5 4.0 Distributed Client/Server
More informationDesigning for Maintainability
Software Testing and Maintenance Designing for Change Jeff Offutt SWE 437 George Mason University 2008 Based on Enterprise Integration Patterns, Hohpe and Woolf, Addison- Wesley, Introduction and Chapter
More informationThe Data Grid: Towards an Architecture for Distributed Management and Analysis of Large Scientific Datasets
The Data Grid: Towards an Architecture for Distributed Management and Analysis of Large Scientific Datasets!! Large data collections appear in many scientific domains like climate studies.!! Users and
More informationPrinciples and characteristics of distributed systems and environments
Principles and characteristics of distributed systems and environments Definition of a distributed system Distributed system is a collection of independent computers that appears to its users as a single
More informationDISTRIBUTED AND PARALLELL DATABASE
DISTRIBUTED AND PARALLELL DATABASE SYSTEMS Tore Risch Uppsala Database Laboratory Department of Information Technology Uppsala University Sweden http://user.it.uu.se/~torer PAGE 1 What is a Distributed
More informationSOACertifiedProfessional.Braindumps.S90-03A.v2014-06-03.by.JANET.100q. Exam Code: S90-03A. Exam Name: SOA Design & Architecture
SOACertifiedProfessional.Braindumps.S90-03A.v2014-06-03.by.JANET.100q Number: S90-03A Passing Score: 800 Time Limit: 120 min File Version: 14.5 http://www.gratisexam.com/ Exam Code: S90-03A Exam Name:
More informationChapter 3. Database Environment - Objectives. Multi-user DBMS Architectures. Teleprocessing. File-Server
Chapter 3 Database Architectures and the Web Transparencies Database Environment - Objectives The meaning of the client server architecture and the advantages of this type of architecture for a DBMS. The
More informationEnterprise Integration EAI vs. SOA vs. ESB
Enterprise Integration EAI vs. SOA vs. ESB Author - Anurag Goel Page 1 of 6 TABLE OF CONTENTS 1 INTRODUCTION... 4 2 SOA... 4 3 EAI... 5 3.1 HUB/SPOKE... 5 3.2 BUS... 7 4 ESB... 9 5 CONCLUSION... 10 6 TAKEAWAYS
More informationAppendix A Core Concepts in SQL Server High Availability and Replication
Appendix A Core Concepts in SQL Server High Availability and Replication Appendix Overview Core Concepts in High Availability Core Concepts in Replication 1 Lesson 1: Core Concepts in High Availability
More informationService Oriented Architecture
Service Oriented Architecture Impact on Information Quality PG 945 John Walsh - Personal GROUP 1 software PG 946 Service Oriented Architecture (SOA) Key Concepts Software functionality is a re-usable service
More informationService Virtualization: Managing Change in a Service-Oriented Architecture
Service Virtualization: Managing Change in a Service-Oriented Architecture Abstract Load balancers, name servers (for example, Domain Name System [DNS]), and stock brokerage services are examples of virtual
More informationCloud Computing and SOA from Enterprise Perspective. Yan Zhao, PhD ArchiTech Consulting LLC yan.zhao@architechllc.com www.architechllc.com Oct.
Cloud Computing and SOA from Enterprise Perspective Yan Zhao, PhD ArchiTech Consulting LLC yan.zhao@architechllc.com www.architechllc.com Oct., 2009 Content Summary The evolution of IT and IT infrastructure,
More informationCOMP5426 Parallel and Distributed Computing. Distributed Systems: Client/Server and Clusters
COMP5426 Parallel and Distributed Computing Distributed Systems: Client/Server and Clusters Client/Server Computing Client Client machines are generally single-user workstations providing a user-friendly
More informationChapter Outline. Chapter 2 Distributed Information Systems Architecture. Middleware for Heterogeneous and Distributed Information Systems
Prof. Dr.-Ing. Stefan Deßloch AG Heterogene Informationssysteme Geb. 36, Raum 329 Tel. 0631/205 3275 dessloch@informatik.uni-kl.de Chapter 2 Architecture Chapter Outline Distributed transactions (quick
More informationIndependent Insight for Service Oriented Practice. An SOA Roadmap. John C. Butler Chief Architect. A CBDI Partner Company. www.cbdiforum.
Independent Insight for Oriented Practice An SOA Roadmap John C. Butler Chief Architect A CBDI Partner Company www.cbdiforum.com Agenda! SOA Vision and Opportunity! SOA Roadmap Concepts and Maturity Levels!
More informationCHAPTER 1: OPERATING SYSTEM FUNDAMENTALS
CHAPTER 1: OPERATING SYSTEM FUNDAMENTALS What is an operating? A collection of software modules to assist programmers in enhancing efficiency, flexibility, and robustness An Extended Machine from the users
More informationDefinition: Software Architecture
Application Servers G22.3033-0 Session 2 Sub-Topic 2 Enterprise Architecture Frameworks (EAFs) & Pattern Driven EAFs Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute
More informationAzure Scalability Prescriptive Architecture using the Enzo Multitenant Framework
Azure Scalability Prescriptive Architecture using the Enzo Multitenant Framework Many corporations and Independent Software Vendors considering cloud computing adoption face a similar challenge: how should
More informationEnergySync and AquaSys. Technology and Architecture
EnergySync and AquaSys Technology and Architecture EnergySync and AquaSys modules Enterprise Inventory Enterprise Assets Enterprise Financials Enterprise Billing Service oriented architecture platform
More informationPlatform Autonomous Custom Scalable Service using Service Oriented Cloud Computing Architecture
Platform Autonomous Custom Scalable Service using Service Oriented Cloud Computing Architecture 1 B. Kamala 2 B. Priya 3 J. M. Nandhini 1 2 3 ABSTRACT The global economic recession and the shrinking budget
More informationReference Model for Cloud Applications CONSIDERATIONS FOR SW VENDORS BUILDING A SAAS SOLUTION
October 2013 Daitan White Paper Reference Model for Cloud Applications CONSIDERATIONS FOR SW VENDORS BUILDING A SAAS SOLUTION Highly Reliable Software Development Services http://www.daitangroup.com Cloud
More informationIntroduction to TIBCO MDM
Introduction to TIBCO MDM 1 Introduction to TIBCO MDM A COMPREHENSIVE AND UNIFIED SINGLE VERSION OF THE TRUTH TIBCO MDM provides the data governance process required to build and maintain a comprehensive
More informationEvent-based middleware services
3 Event-based middleware services The term event service has different definitions. In general, an event service connects producers of information and interested consumers. The service acquires events
More informationzen Platform technical white paper
zen Platform technical white paper The zen Platform as Strategic Business Platform The increasing use of application servers as standard paradigm for the development of business critical applications meant
More informationBig Data Management and NoSQL Databases
NDBI040 Big Data Management and NoSQL Databases Lecture 4. Basic Principles Doc. RNDr. Irena Holubova, Ph.D. holubova@ksi.mff.cuni.cz http://www.ksi.mff.cuni.cz/~holubova/ndbi040/ NoSQL Overview Main objective:
More informationUnderstanding Neo4j Scalability
Understanding Neo4j Scalability David Montag January 2013 Understanding Neo4j Scalability Scalability means different things to different people. Common traits associated include: 1. Redundancy in the
More informationThe Sierra Clustered Database Engine, the technology at the heart of
A New Approach: Clustrix Sierra Database Engine The Sierra Clustered Database Engine, the technology at the heart of the Clustrix solution, is a shared-nothing environment that includes the Sierra Parallel
More informationGetting Real Real Time Data Integration Patterns and Architectures
Getting Real Real Time Data Integration Patterns and Architectures Nelson Petracek Senior Director, Enterprise Technology Architecture Informatica Digital Government Institute s Enterprise Architecture
More informationCSCW and Software Engineering Dr.-Ing. Stefan Werner
CSCW and Software Engineering Dr.-Ing. Stefan Werner Chapter 6: Groupware Architectures Slide 1of 26 Content 1. Introduction to Global Engineering 2 Introduction to CSCW and Groupware 3. Groups and Group
More informationAn Oracle White Paper October 2013. Oracle Data Integrator 12c New Features Overview
An Oracle White Paper October 2013 Oracle Data Integrator 12c Disclaimer This document is for informational purposes. It is not a commitment to deliver any material, code, or functionality, and should
More informationEnterprise Application Integration - An Overview. Prepared By
Enterprise Application Integration - An Overview Prepared By TABLE OF CONTENTS 1. ABOUT EAI... 3 2. REASONS FOR EMERGENCE OF EAI... 3 3. ADVANTAGES OF IMPLEMENTING EAI... 4 4. EAI FUNCTIONING... 4 5. EAI
More informationA Grid Architecture for Manufacturing Database System
Database Systems Journal vol. II, no. 2/2011 23 A Grid Architecture for Manufacturing Database System Laurentiu CIOVICĂ, Constantin Daniel AVRAM Economic Informatics Department, Academy of Economic Studies
More informationThis paper defines as "Classical"
Principles of Transactional Approach in the Classical Web-based Systems and the Cloud Computing Systems - Comparative Analysis Vanya Lazarova * Summary: This article presents a comparative analysis of
More informationCloud Computing Patterns Fundamentals to Design, Build, and Manage Cloud Applications
Cloud Computing Patterns Fundamentals to Design, Build, and Manage Cloud Applications Christoph Fehling Institute of Architecture of Application Systems University of Stuttgart Universitätsstr. 38 70569
More informationE) Modeling Insights: Patterns and Anti-patterns
Murray Woodside, July 2002 Techniques for Deriving Performance Models from Software Designs Murray Woodside Second Part Outline ) Conceptual framework and scenarios ) Layered systems and models C) uilding
More informationJOURNAL OF OBJECT TECHNOLOGY
JOURNAL OF OBJECT TECHNOLOGY Online at www.jot.fm. Published by ETH Zurich, Chair of Software Engineering JOT, 2008 Vol. 7 No. 7, September-October 2008 Applications At Your Service Mahesh H. Dodani, IBM,
More informationMODEL DRIVEN DEVELOPMENT OF BUSINESS PROCESS MONITORING AND CONTROL SYSTEMS
MODEL DRIVEN DEVELOPMENT OF BUSINESS PROCESS MONITORING AND CONTROL SYSTEMS Tao Yu Department of Computer Science, University of California at Irvine, USA Email: tyu1@uci.edu Jun-Jang Jeng IBM T.J. Watson
More informationDistributed Objects and Components
Distributed Objects and Components Introduction This essay will identify the differences between objects and components and what it means for a component to be distributed. It will also examine the Java
More information