An Azure of Things, a developer’s perspective
Download as PPTX, PDF0 likes599 views
The world of integration is changing very quickly and we have the opportunity to use a lot of different technologies. There are many ways to solve the same problem and new technologies being introduced all of the time. Azure is now full of very interesting features and the real challenge is understanding how to use and combine all of these together in an effective way to create a good solution. In this session Nino will talk about his experiences and thoughts from the last year around areas such as BizTalk, Hybrid Integration, Microservices, Event Hubs, Stream Analytics and more.
More Related Content
What's hot (20)
Similar to An Azure of Things, a developer’s perspective (20)
More from BizTalk360 (20)
Recently uploaded (20)
An Azure of Things, a developer’s perspective
- 1. tSponsors Nino Crudele Integration MVP, Solidsoft Reply, Principal Consultant An Azure of Things, a developer’s perspective BizTalk Summit 2015 – London ExCeL London | April 13th & 14th
- 12. 2015 What the most used is?
- 13. File• Simple to manage • Fast to use • Polymorphic • Adaptable • Serializable • Full extensible • Persistent • Multi platform • Scalable (size) • Reliable
- 15. Peer To Peer (Spaghetti Integration) Approach 1
- 16. Approach 2 Transports / Connectors Integration Framework TransformationRulesRouting Brokering Logic Management
- 17. Integration Framework Approach 3 Transports / Connectors TransformationRulesRouting Brokering Logic Management Proxy Transports / Connectors
- 18. What I would really like by an Integration framework? • Simple to manage • Fast to use • Polymorphic • Adaptable • Serializable • Full extensible • Persistent • Multi platform • Scalable • Reliable File
- 19. Azure stack Cloud On Premise Cloud & Bridging Technologies Service Bus MessagingService Bus Relay VPN BizTalk Services EAI Azure BizTalk VM BizTalk Server 2013 R2 Windows Server AppFabric Windows Server Service Bus Windows Server Workflow Manager SQL Server Integration Services WCF Routing Service Custom WCF ServicesFrameworks & Foundation .net WCF WF SOAP REST AMQP Azure XML/XSD XSLT JSON Traffic Manager BizTalk Services EDI BizTalk Hybrid Connections Express Route BizTalk Adapter Service Azure Active Directory Access Control Service Azure Web Sites Notification Hubs Web & Worker Roles Cache Azure SQL DB Document DB Scheduler Azure Automation Stream Analytics Event Hubs API Management Virtual Network Data Factory
- 22. {}JiTGate Core Technology stack • .Net Framework • Json • REST • PowerShell • Microsoft Roslyn • Visual Studio Extension • Swagger •Azure Event Hubs •Azure Blob •Azure Topics •Azure Queue •Azure Table •Azure Worker Role •Azure Stream Analytic •Azure API APPS
- 23. Introducing Azure Event Hubs Event Producers Azure Event Hub > 1M Producers > 1GB/sec Aggregate Throughput Up to 32 partitions via portal, more on request Partitions Direct PartitionKey Hash Throughput Units: • 1 ≤ TUs ≤ Partition Count • TU: 1 MB/s writes, 2 MB/s reads Consumer Group(s) Receivers AMQP 1.0 Credit-based flow control Client-side cursors Offset by Id or Timestamp Event Processor Host IEventProcessor
- 24. Microsoft Cloud & Mobility Summit 14 A simple sample
- 25. JiTGate Just in Time Gate
- 26. JitGate Key features • Fast and Simple to install • Event Propagation based • Event Bubbling, Capturing • Multi transports protocol • Azure Event Hubs (Primary) • Queue, Topics, Relay, Blob, Table • Multi Pub/Sub scenarios • 1To1 - 1To∞ - ∞To1 - ∞To∞ • High Scale (Million messages X second) • High Thread Performance (200.000 events X second) • Convention Over Configuration based • Web API / REST
- 27. JitPoint Key features • Fast and Simple to activate and to extend • Multi versions • NT Service, Simple Console App, Worker Role, DLL extension, API APPS • Multi Instances • Automatic Synchronization • Shared Configuration • Extensible Configuration patterns (Json based) • Stream based • Console App and Visual Studio Package (vNext) • Web Api (vNext) • Cluster able (vNext) • Convention Over Configuration behavior • Web API / REST
- 28. Trigger and Events Key features • Fast and Simple to create • Extensible language • .Net • Powershell • .Net Scripting • Base templates ready, File, FTP, Relay, REST, SQL, Event Hubs, Blob, Table, Queue, Topic, Event Viewer, ETW , RFID, coming soon (API APPS, Oracle, ..) • Object Relational Auto mapping • Complex hierarchical call pattern • Trigger To Events – Events To Events – Events To Trigger • Extensible property configuration pattern (pure Json, Json + Powershell, Json + .Net) • Multi instance mechanism, Polling, Single instance, Notification Handling • Shared and Serializable • Convention Over Configuration activation • Web API / REST
- 29. Engine Key features • Extensible Rule Engine based on Roslyn • Correlation mechanism ready • Extensible Reliable patterns • Client file • Database • Blob • Table Storage • Extensible Fast Logging • ETW • SQL Azure • Table Storage • BLOB
- 31. Provisioning Copy Synchronization JitPoint JitPoint JitPointJitPoint JitPoint Configuration JIT Execution Triggers Actions Properties Events Actions Properties Build
- 32. Trigger activation Triggers Actions Properties Events Actions Properties Polling Databases ,Files Blob, Table, FTP POP3 Single Instance REST, WCF, Queue, Topic, Relay Event Handler RFID, Event Handling, Event Viewer, ETW http://localhost:8000/JitGate/ExecuteTrigger?TriggerID={9A989BD1-C8DE-4FC1-B4BA-02E7D8A4AD7} REST Service Call Application Call Scheduling Events Actions Properties Events Actions Properties Events Actions Properties CorrelationEvents Actions Properties Rule
- 33. Demo
- 34. My pipeline • Back Italy and relax • Back in UK and do some skateboarding • Multi Event Hubs distribution • Logging • More Trigger and Event templates (API APPS) • Transformation • Visual Studio Extension • NT Version • Clutering • Worker Role version
- 36. Q&A Nino Crudele http://ninocrudele.me [email protected] @ninocrudele Microsoft Application Integration MVP
- 37. >- * Thank You
Editor's Notes
- #3: Sapete il perche di questa imagine?
- #4: Is not technology only is friendship
- #5: Sapete il perche di questa imagine?
- #6: Sapete il perche di questa imagine?
- #7: Sapete il perche di questa imagine?
- #8: Sapete il perche di questa imagine?
- #9: Voglio parlare di integrazione How long are you in the integration field? Chi ri ricorda cosa si usava per integrare?
- #11: Abbiamo avuto una fantastica evoluzione Ma dopo tutti questi anni quale e il piu usato?
- #12: Sapete il perche di questa imagine?
- #14: Il File, curioso vero? Perche e semplice da maneggiare, facile da gestire ed e universalmente conosciuto
- #15: Un integration point e un punto di integrazione generic, potremmo dover integrare qualsiasi cosa e non per questo essere in grado di adattarci
- #16: Tutti integrano tutti
- #17: Forniscono un loro adaptation suite e un unico framewoek che ingloba tutto
- #18: Tutto in un punto
- #19: Mediation, adaptation… Cosa voglio? Che faccia almeno quello che un file e capace di fornire
- #22: Mediation, adaptation… Cosa voglio? Che faccia almeno quello che un file e capace di fornire
- #26: Un integration point e un punto di integrazione generic, potremmo dover integrare qualsiasi cosa e non per questo essere in grado di adattarci
- #27: Puoi cambiare il Dynamic Reliable patterns su file, blob o dataset o creare il tuo
- #31: A sigle integration point is able to offer the total extension
- #32: A sigle integration point is able to offer the total extension
- #33: A sigle integration point is able to offer the total extension
- #34: Un integration point e un punto di integrazione generic, potremmo dover integrare qualsiasi cosa e non per questo essere in grado di adattarci