Architecture Quality extraordinarily large systems, services, strategic design, scalability and reliability, large datasets, latency, service- oriented.

Slides:



Advertisements
Similar presentations
SOA for EGovernment 1 Emergency Services Enterprise Framework: A Service-Oriented Approach Sukumar Dwarkanath COMCARE Michael Daconta Oberon Associates.
Advertisements

Why am I here Development techniques are headed down the wrong path! Our world should be getting simpler – it is not The solutions that will solve the.
Introducing Campus Networks
Spring, Hibernate and Web Services 13 th September 2014.
Enhanced visibility with Actional and Sonic ESB Frank Beusenberg Applied Technology Consultant Mahesh Nair Software Architect Kim Palko Sr. Product Manager.
Not all of a large system will be well designed..
Agent and Object Technology Lab Dipartimento di Ingegneria dell’Informazione Università degli Studi di Parma AOT LAB LAB Using Agent Technology as a Support.
OASIS Reference Model for Service Oriented Architecture 1.0
SOA with Progress Philipp Walther Consultant. © 2007 Progress Software Corporation2 Agenda  SOA  Enterprise Service Bus (ESB)  The Progress SOA Portfolio.
Why static is bad! Hadoop Pregel MPI Shared cluster Today: static partitioningWant dynamic sharing.
Domain Modelling Paul Stovell. Architecture: Implicit or Explicit? Architecture exists implicitly But if you don’t define it, it probably sucks.
Review Amit Shabtay. March 3rd, 2004 Object Oriented Design Course 2 Review What have we done during the course? Where to learn more? What is for the.
Effective systems development requires a team effort from stakeholders, users, managers, systems development specialists, and various support personnel,
21-February-2003cse Architecture © 2003 University of Washington1 Architecture CSE 403, Winter 2003 Software Engineering
Welcome Jason McConnell Developer Evangelist Microsoft Australia
Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica System architectures Updated: November 2014.
Real-Time Systems and Programming Languages
Agent-Based Acceptability-Oriented Computing International Symposium on Software Reliability Engineering Fast Abstract by Shana Hyvat.
J2EE vs..NET Tom Tong. Enterprise Application 1 distributed 2 multiple-platform 3 critical 4 performance 5 security 6 multiple-data sources.
Systems Integration & Consulting June Copyright ® 2009 Ayenda Agenda Introduction to Systems Integration System Integration Challenges and Opportunities.
Chapter 9: Moving to Design
Introduction to EJB INFORMATICS ENGINEERING – UNIVERSITY OF BRAWIJAYA Eriq Muhammad Adams J
Architectural Design Establishing the overall structure of a software system Objectives To introduce architectural design and to discuss its importance.
Jens Haeusser Director, Strategy IT, UBC Open Source, Community Source, and SOA Seminars in Academic Computing, Directors Leadership Seminar, August 7,
Word Wide Cache Distributed Caching for the Distributed Enterprise.
Cloud MapReduce : a MapReduce Implementation on top of a Cloud Operating System Speaker : 童耀民 MA1G Authors: Huan Liu, Dan Orban Accenture.
Chapter 9 Moving to Design Part 2.
Chapter 9 Elements of Systems Design
© Drexel University Software Engineering Research Group (SERG) 1 Based on the paper by Philippe Kruchten from Rational Software.
The Data Grid: Towards an Architecture for the Distributed Management and Analysis of Large Scientific Dataset Caitlin Minteer & Kelly Clynes.
Mesos A Platform for Fine-Grained Resource Sharing in the Data Center Benjamin Hindman, Andy Konwinski, Matei Zaharia, Ali Ghodsi, Anthony Joseph, Randy.
How eNet4S can benefit your project? eNet4S Software Solution Business Team Chief Technology Officer July 11, 2006.
Application of Provenance for Automated and Research Driven Workflows Tara Gibson June 17, 2008.
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Design Patterns Introduction What is a Design Pattern? Why were they developed? Why should we use them? How important are they?
Domain and Persistence Patterns. Fundamental Pattern Types Design Patterns Business Logic Patterns.
Service - Oriented Middleware for Distributed Data Mining on the Grid ,劉妘鑏 Antonio C., Domenico T., and Paolo T. Journal of Parallel and Distributed.
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Chapter 1: Introduction to Scaling Networks Scaling Networks.
© 2008, Cognizant Technology Solutions. All Rights Reserved. The information contained herein is subject to change without notice. BPO: Technology- driven.
Systems Analysis and Design in a Changing World, Fourth Edition
9 Systems Analysis and Design in a Changing World, Fourth Edition.
9 Systems Analysis and Design in a Changing World, Fourth Edition.
SOA for Support and Maintenance Steve Jones Head of SOA, Global Outsourcing, Capgemini.
The Government And Service Oriented Architecture Presented by: Dan Pelman.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
Domain Driven Design Using.NET Dave Rael. What’s wrong with this code? Public void CallMethodThatMightThrowScaryException(int carelessInputWithoutValidation)
Software Engineering for Capstone Courses Richard Anderson CSE 481b Winter 2007.
Architecture Quality extraordinarily large systems, services, strategic design, scalability and reliability, large datasets, latency, service-oriented.
Carnegie Mellon University © Robert T. Monroe Management Information Systems Cloud Computing I Cloud Models and Technologies Management.
A Platform for Fine-Grained Resource Sharing in the Data Center
Teen Suicide By: Yoyo E10-2. Summary Tragedy of a young teen dying due to overwhelming hopelessness or frustration which could be lead to family, friends,
V-Shaped Software Development Life Cycle Model. Introduction: Variation of water fall model. Same sequence structure as water fall model. Strong emphasis.
1 Acquisition Automation – Challenges and Pitfalls Breakout Session # E11 Name: Jim Hargrove and Allen Edgar Date: Tuesday, July 31, 2012 Time: 2:30 pm-3:45.
9 Systems Analysis and Design in a Changing World, Fifth Edition.
AMSA TO 4 Advanced Technology for Sensor Clouds 09 May 2012 Anabas Inc. Indiana University.
Dr. Ir. Yeffry Handoko Putra
Data Services for Service Oriented Architecture in Finance
SuperComputing 2003 “The Great Academia / Industry Grid Debate” ?
Developing Applications
Jens Haeusser Director, Strategy IT, UBC
Enterprise Service Bus (ESB) (Chapter 9)
Introduction To System Analysis and Design PART 2
SOA-1: Fundamentals of Service-Oriented Architecture
Björn Hasselgren, PhD “Shaping the Future of Core Network Corridors”
Quality Assurance for Component-Based Software Development
Physics data processing with SOA
Defining the Grid Fabrizio Gagliardi EMEA Director Technical Computing
Strategic Sponsors Sponsors and Partners Gold Sponsors Silver Sponsors.
Introduction to SOA Part II: SOA in the enterprise
Presentation transcript:

Architecture Quality extraordinarily large systems, services, strategic design, scalability and reliability, large datasets, latency, service- oriented systems, manage architectural change, scaling domain driven design

Richard Gabriel - Extraordinarly large systems  Can there be an architecture for extraordinarily large systems?  Does it matter?  Forgiving/unforgiving parts of a system  Path of correctness is wide  Digital evolution/genetic algorithms  Augment modules with; test, repair, clone, suicide.

Nati Shalom - Scaling Tier-based systems  Traditional Tier-based systems suffer from over-communication  Scaling them is painful  3 steps; –In-memory data grid –Consolidate the ESB and data together –Assemble business logic, data and messaging  Now it is scalable

Eric Evans - Strategic Design  Not all of a large system will be well designed  Domain: A sphere of knowledge, influence, or activity  Model: A system of abstractions that describes selected aspects a domain and can be used to solve problems related to that domain.  Distill the core domain; –What makes your system worth writing? –Why not buy it off the shelf? –Why not outsource it?  Be recognized for what you do!

Cameron Purdy - Scalability and Reliability  Scalability vs. Performance  How to avoid scalability and reliability. By overusing databases for things they are not useful for, and overusing abstraction, and introducing single points of failure, and single points of bottlenecks, and reinventing the wheel by building your own infrastructure  Use common sense (it is not as common as you might think)

Jinesh Varia - Hadoop  Java based framework, that enables you to stop worrying about about details such as concurrency  Another layer of abstraction to enable the database to just be the database (which it is good at)

The speakers of the track today  “Architect for Latency” Dan Pritchett  “Guerrilla SOA” Jim Webber  “How to Work With Business Leaders to Manage Architectural Change” Luke Hohmann  “Scaling Domain Driven Design” Greg Young

Panel this afternoon Moderator: Ramano Rao Panelists: Luke Hohmann, Greg Young, Eric Evans, Nati Shalom, Dan Pritchett  A two-sentence summary of the most important part of their presentation  The most critical things to be thought about in the very early days of a new project or a new cycle.