Use Cases Atomic Patterns 1 Axel Angeli - (c) 2009 logosworld.com - Building the SOA City.

Slides:



Advertisements
Similar presentations
Introduction 2 1: Introduction.
Advertisements

1 IK1500 Communication Systems IK1330 Lecture 3: Networking Anders Västberg
TLS Introduction 14.2 TLS Record Protocol 14.3 TLS Handshake Protocol 14.4 Summary.
OSI MODEL Maninder Kaur
Answers of Exercise 7 1. Explain what are the connection-oriented communication and the connectionless communication. Give some examples for each of the.
Computer Networks and the Internet CMPT 109 Montclair State University.
Click to add text Introduction to z/OS Basics © 2006 IBM Corporation Chapter 15: WebSphere MQ.
CMPE 80N - Introduction to Networks and the Internet 1 CMPE 80N Winter 2004 Lecture 18 Introduction to Networks and the Internet.
Optimistic Virtual Synchrony Jeremy Sussman - IBM T.J.Watson Idit Keidar – MIT LCS Keith Marzullo – UCSD CS Dept.
Chapter 2 Network Models.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Communicating over the Network Network Fundamentals – Chapter 2.
Communication Part II Message-Oriented Communication Chapter 4.
Messaging Passing Communication AOS Dan Huang. Why Need Message RPC and ROI hiding communication for transparency. Hiding communication is not an appropriate.
Lecture slides prepared for “Business Data Communications”, 7/e, by William Stallings and Tom Case, Chapter 8 “TCP/IP”.
Module A Panko and Panko Business Data Networks and Security, 9 th Edition © 2013 Pearson.
C8: Enterprise Integration Patterns in Sonic ™ ESB Stefano Picozzi Solutions Architect.
Connector Types Interaction services broadly categorize connectors Many details are left unexplained. They fail to provide enough detail to be used in.
CPT 499 Internet Skills for Educators Electronic Mail Session Five.
Protocol Architectures. Simple Protocol Architecture Not an actual architecture, but a model for how they work Similar to “pseudocode,” used for teaching.
Local Area Networks (LAN) are small networks, with a short distance for the cables to run, typically a room, a floor, or a building. - LANs are limited.
CS 447 Networks and Data Communication
Kashif Bashir Chapter 2 Network Models.
CH2 System models.
 An ISO is a multi national body dedicated to worldwide agreement on international standards.  An ISO standard that covers all aspects of network communications.
EITnotes.com For more notes and topics visit:
TCP/IP Transport and Application (Topic 6)
More on TCP Acknowledgements Sequence Number Field Initial Sequence Number Acknowledgement Number Field.
(Business) Process Centric Exchanges
Chapter 22 Q and A Victor Norman CS 332 Spring 2014.
A Scalable Content-Addressable Network (CAN) Seminar “Peer-to-peer Information Systems” Speaker Vladimir Eske Advisor Dr. Ralf Schenkel November 2003.
MODULE I NETWORKING CONCEPTS.
Chapter 15 – Part 2 Networks The Internal Operating System The Architecture of Computer Hardware and Systems Software: An Information Technology Approach.
Content Addressable Networks CAN is a distributed infrastructure, that provides hash table-like functionality on Internet-like scales. Keys hashed into.
Supporting Systolic and Memory Communication in iWarp CS258 Paper Summary Computer Science Jaein Jeong.
Enterprise Integration Patterns CS3300 Fall 2015.
Multimedia and Networks. Protocols (rules) Rules governing the exchange of data over networks Conceptually organized into stacked layers – Application-oriented.
Infrastructure Service Approach to Handling Security in Service-Oriented Architecture Business Applications Doina Iepuras.
Chapter 24 Transport Control Protocol (TCP) Layer 4 protocol Responsible for reliable end-to-end transmission Provides illusion of reliable network to.
1 010/02 Aspect-Oriented Interceptors Pattern 1/4/2016 ACP4IS 2003John Zinky BBN Technologies Aspect-Oriented Interceptors Pattern Dynamic Cross-Cutting.
AMQP, Message Broker Babu Ram Dawadi. overview Why MOM architecture? Messaging broker like RabbitMQ in brief RabbitMQ AMQP – What is it ?
Seminar on Service Oriented Architecture Distributed Systems Architectural Models From Coulouris, 5 th Ed. SOA Seminar Coulouris 5Ed.1.
8/28/ Network Models - Lin 1 CPET/ECET Network Models Data Communications and Networking Fall 2004 Professor Paul I-Hai Lin Electrical and.
 Program Abstractions  Concepts  ACE Structure.
Christian Stiller Technical Account Manager SOA-23: Enterprise Integration Patterns in Sonic ™ ESB.
1 Switching and Forwarding Sections Connecting More Than Two Hosts Multi-access link: Ethernet, wireless –Single physical link, shared by multiple.
An End-to-End Service Architecture r Provide assured service, premium service, and best effort service (RFC 2638) Assured service: provide reliable service.
Mr. Sathish Kumar. M Department of Electronics and Communication Engineering I’ve learned that people will forget what you said, people will forget what.
Group Communication A group is a collection of users sharing some common interest.Group-based activities are steadily increasing. There are many types.
BASICS Gabriella Paolini (GARR) 27/05/11 - ICCU Roma 1 How INTERNET works !
OSI Model OSI MODEL. Communication Architecture Strategy for connecting host computers and other communicating equipment. Defines necessary elements for.
OSI Model OSI MODEL.
Key Distribution in DTNs
Chapter 4 Introduction to Network Layer
THE OSI MODEL By: Omari Dasent.
The ISO OSI Reference Model
Telemedicine.
Understanding the OSI Reference Model
IOS Network Model 2nd semester
Chapter 4 Introduction to Network Layer
Exploring the Cloud Marketplace
Enterprise Service Bus
Hidden Power : Service Broker
Network Layer The network layer is responsible for the source-to-destination delivery of a packet, possibly across multiple networks (links). Whereas the.
Networking.
OSI Model OSI MODEL.
Voice in the Cloud.
Introduction to SOA Author: Axel Angeli Logosworld.com
WJEC GCSE Computer Science
Chapter 6 – Distributed Processing and File Systems
Author: Axel Angeli Logosworld.com
Presentation transcript:

Use Cases Atomic Patterns 1 Axel Angeli - (c) 2009 logosworld.com - Building the SOA City

2

Secure Distribution Enhancing security of message passage by sending chunks via different routes 3 Axel Angeli - (c) 2009 logosworld.com - Building the SOA City

Write and and store it locally A service will pick up the message Message delivered on receiver Write and and store it locally A service will pick up the message Message delivered on receiver Jigsaw a message in many small elements and send every piece via a random path at different times 4 Axel Angeli - (c) 2009 logosworld.com - Building the SOA City

Pattern Based Message Flow  Tear the message apart  Send each clip separately  Re-join the clips to the full message The application is designed to transfer a message in several small pieces to a peer destination. This can be used to transfer large messages in parallel, enhance security or to enhance reliability through redundant sending of parts.    5 Axel Angeli - (c) 2009 logosworld.com - Building the SOA City

 Message imported to local store  Message is treated by a service  Chunks are stored in queues  Chunks replicated to remote queues  Message is reassembled  Message imported to local store  Message is treated by a service  Chunks are stored in queues  Chunks replicated to remote queues  Message is reassembled How it works 6 Axel Angeli - (c) 2009 logosworld.com - Building the SOA City

 Enhance transfer security Only small clips can be intercepted and abducted  Enhance reliability Send clips redundantly  Channel bundling Accelerate transfer by using parallel channels  Enhance transfer security Only small clips can be intercepted and abducted  Enhance reliability Send clips redundantly  Channel bundling Accelerate transfer by using parallel channels Use Cases 7 Axel Angeli - (c) 2009 logosworld.com - Building the SOA City

Interface Pipe Collector Store & Forward (Pipe) Splitter Interface Pipe Pattern Based Message Flow Split, Store&Forward and Collect This example is used to split a message and send it over in parallel chunks to a receiver. The sender side chunks the message and puts them in queues; then a store&forward mechanism replicates the queue; the receiver takes the messages from the queue and reassembles them. Q1Q1Q1Q1 Q2Q2Q2Q2 Q3Q3Q3Q3 Q‘1Q‘1Q‘1Q‘1 Q’ 2 Q’ 3 8 Axel Angeli - (c) 2009 logosworld.com - Building the SOA City

9

10 Axel Angeli - (c) 2009 logosworld.com - Building the SOA City

Noise Reduction Mass message transfer is always accompanied by noice – unwanted and redundant extra information 11 Axel Angeli - (c) 2009 logosworld.com - Building the SOA City

One queue is used to receive any message, another queue holds the cleansed messages only Collect all messages in a message queue and consolidate the duplicates 12 Axel Angeli - (c) 2009 logosworld.com - Building the SOA City

Pattern Based Message Flow  Tear the message apart  Send each clip separately  Re-join the clips to the full message The application is designed to transfer a message in several small pieces to a peer destination. This can be used to transfer large messages in parallel, enhance security or to enhance reliability through redundant sending of parts.    13 Axel Angeli - (c) 2009 logosworld.com - Building the SOA City

 Message imported to local store  Message is treated by a service  Chunks are stored in queues  Chunks replicated to remote queues  Message is reassembled  Message imported to local store  Message is treated by a service  Chunks are stored in queues  Chunks replicated to remote queues  Message is reassembled How it works 14 Axel Angeli - (c) 2009 logosworld.com - Building the SOA City

 Enhance transfer security Only small clips can be intercepted and abducted  Enhance reliability Send clips redundantly  Channel bundling Accelerate transfer by using parallel channels  Enhance transfer security Only small clips can be intercepted and abducted  Enhance reliability Send clips redundantly  Channel bundling Accelerate transfer by using parallel channels Use Cases 15 Axel Angeli - (c) 2009 logosworld.com - Building the SOA City

Interface Pipe Collector Store & Forward (Pipe) Splitter Interface Pipe Pattern Based Message Flow Split, Store&Forward and Collect This example is used to split a message and send it over in parallel chunks to a receiver. The sender side chunks the message and puts them in queues; then a store&forward mechanism replicates the queue; the receiver takes the messages from the queue and reassembles them. Q1Q1Q1Q1 Q2Q2Q2Q2 Q3Q3Q3Q3 Q‘1Q‘1Q‘1Q‘1 Q’ 2 Q’ 3 16 Axel Angeli - (c) 2009 logosworld.com - Building the SOA City

17 Axel Angeli - (c) 2009 logosworld.com - Building the SOA City

18 Axel Angeli - (c) 2009 logosworld.com - Building the SOA City