Seminario Enterprise Integration Patterns
•
3 gefällt mir•1,900 views
Introduzione agli Entrprise Integration Patterns per Studenti di TLC - Slide a supporto del seminario
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Ähnlich wie Seminario Enterprise Integration Patterns
Ähnlich wie Seminario Enterprise Integration Patterns (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Seminario Enterprise Integration Patterns
- 1. Enterprise Integration Patterns for TLC by Cristiano Costantini
- 2. Introduzione
- 3. “Integrare” Cosa si intende quando parliamo di integrazione? Trovare una soluzione al seguente problema: “Come posso far funzionare insieme molteplici applicazioni attraverso lo scambio di informazioni?” 3
- 4. Enterprise Integration Patterns (EIP) Gli Enterprise Integration Patters offrono soluzioni per affrontare il precedente problema. Cosa sono gli EIP? 4
- 5. Un libro! Gregor Hohpe and Bobby Woolf Addison-Wesley 2003 5
- 6. Perchè “integrare” è importante? Integrare è quindi l’arte di spostare informazioni da una applicazione ad un altra: 6 (soprattutto per studenti TLC) I corsi universitari vi insegnano le tecnologie per spostare informazioni (su reti); Gli EIP vi insegnano come organizzare bene questo trasferimento di informazioni su sistemi ICT.
- 7. Come si può fare integrazione? I principali metodi tramite cui avviene integrazione nei sistemi software sono: 7
- 11. Messaging Gli EIP si focalizzano sulla integrazione via “messaging” e definiscono una propria notazione per rappresentare le soluzioni di integrazione. 11
- 16. Catalogo Pattern
- 17. Organizzazione degli EIP 17 Chapter 1: Integration Styles Chapter 2: Messaging Systems Chapter 3: Messaging Channels Chapter 4: Message Construction Chapter 5: Message Routing Chapter 6: Message Transformation Chapter 7: Messaging Endpoints Chapter 8: Systems Management Messaging Message Channel Message Pipes and Filters Message Router Message Translator Message Endpoint File Transfer Shared Database RMI
- 19. Message Channel “How does one application communicate with another using messaging?” 19 Messaging Systems
- 20. Message “How can two applications connected by a message channel exchange a piece of information?” 20 Messaging Systems
- 21. Pipes and Filters “How can we perform complex processing on a message while maintaining independence and flexibility?” 21 Messaging Systems
- 22. Message Routing “How can you decouple individual processing steps so that messages can be passed to different filters depending on a set of conditions?” 22 Messaging Systems
- 23. Message Translator “How can systems using different data formats communicate with each other using messaging?” 23 Messaging Systems
- 24. Message Endpoint “How does an application connect to a messaging channel to send and receive messages?” 24 Messaging Systems
- 25. Patterns per “Messaging Channels” 25
- 26. Point-to-Point channel “How can the caller be sure that exactly one receiver will receive the document or perform the call?” 26 Patterns per “Messaging Channels”
- 27. Publish-Subscribe channel “How can the sender broadcast an event to all interested receivers?” 27 Patterns per “Messaging Channels”
- 28. Dead-Letter channel “What will the messaging system do with a message it cannot deliver?” 28 Patterns per “Messaging Channels”
- 29. Patterns per “Message Construction” 29
- 30. Command Message “How can messaging be used to invoke a procedure in another application?” 30 Patterns per “Message Construction”
- 31. Document Message “How can messaging be used to transfer data between applications?” 31 Patterns per “Message Construction”
- 32. Event Message “How can messaging be used to transmit events from one application to another?” 32 Patterns per “Message Construction”
- 33. Request Reply “When an application sends a message, how can it get a response from the receiver?” 33 Patterns per “Message Construction”
- 34. Patterns per “Message Routing” e “Message Transformation” 34
- 35. Message Broker “How can you decouple the destination of a message from the sender and maintain central control over the flow of messages?” 35 Patterns per “Message Routing”
- 36. Canonical Data Model “How can you minimize dependencies when integrating applications that use different data formats?” 36 Patterns per “Message Transformation”
- 37. Patterns per “Messaging Endpoints” 37
- 38. Polling Consumer “How can an application consume a message when the application is ready?” 38 Patterns per “Messaging Endpoints”
- 39. Event Driven Consumer “How can an application automatically consume messages as they become available?” 39 Patterns per “Messaging Endpoints”
- 40. Service Activator “How can an application design a service to be invoked both via various messaging technologies and via non-messaging techniques?” 40 Patterns per “Messaging Endpoints”
- 41. SensorMix Un esempio di architettura software basata su EIP
- 43. SensorMix 43 Rotte di integrazione campionamenti dai sensori
- 44. SensorMix 44 Considerazione sull’uso del Canonical Data Model
- 47. SensorMix Slides: http://cristcost.github.io/sensormix/ Sensormix: https://github.com/cristcost/sensormix/ Sensormix Android: https://github.com/cristcost/sensormix-android/ Sensormix Arduino: https://github.com/michelefi/sensormix-arduino/ 47 Collegamenti:
- 48. Conclusioni
- 49. Libri •Enterprise Integration Patterns -G. Hohpe, B. Woolf - Addison Wesley 49