Amit R Bhatia / Puneeth Nayak Escalation Engineer, Microsoft Integration made easy with Azure Service Bus/APIM

Integrate legacy system Publish APIs hosted on-premise to partners Automated process to extract the text from images and store to durable storage Ensuring Scalability, Durability, Reliability

Users of today

What is Service Bus? Service Bus provides a multi-tenant service for connecting applications through the cloud. Four different communication mechanisms Relay Queue Topic Event Hub Relay – Hybrid application, Expose services/APIs behind Firewall & NAT over internet Queue – Brokered messaging, durability with minimal latency and reliable delivery Topic – Brokered messaging, pub – sub communication model

ServiceBus Architecture Messaging Broker Partition 4 Entity ZZ Messaging Store Partition 1 Gateway Entity D Entity E Partition 2 Entity C Gateway Store Entity A Entity B Partition 3 Entity XX

Relay vs. Message Broker The Relay routes messages ‘straight through’ with feedback path and network backpressure into sender S R Route AuthN/Z Backpressure Feedback Relay Query Filter Pull Broker Brokers hold messages for retrieval and querying

SB Brokered Message Communication - Queue Producer1 M2 M1 Consumer1 Queue (no Session) M4 M3 M2 M1 Consumer2 M3 M4 Producer2 Producer1 M4 Grp1 M1 Consumer1 Queue (Session support) M4 Grp1 M3 Grp2 M2 M1 Consumer2 M3 Grp2 M2 Producer2

SB Brokered Message Communication - Topic Consumer1 Topic 1 Producer1 (M2, M4..) Consumer2 Subscription1 M3 M4 Filter=true M4 M3 M2 M1 Subscription2 M2 M1 Filter=true Producer2 (M1, M3..) Consumer1 M3 M4 Consumer2

ServiceBus Relay Message Communication Control Message with client location (directIP) 4 Gateway Gateway Gateway 3 Client Connects To Servicebus 1 Server Connects To Servicebus OneWay Control Channel-Port 9351 2 Create Listener Messages are streamed 6 3 Relay lookup Gateway store 2 Server Redirected to Gateway – Port 9351 5 Server rendezvous with client on direct IP -Port 9351 Azure VIP/LB Control Message to service with DirectIP of client 4 Enterprise WCF Service WebHTTP Binding (uses TCP transport for listening) HTTP / REST Access (WebHttp Bindings) – Port 80/443

SB Brokered Message Communication

API Management How do you engage with developers? How do you reduce TTFSC? How do you enforce your business policies? How do you make your legacy API modern? How do you understand their behavior? How do you protect your core business systems? API Management

Azure API Management Facade Middleware Monitoring Developer API consumers AZURE API MANAGEMENT Facade decouple modernize optimize ... Middleware secure protect cache ... Monitoring usage health monetization ... Developer discover document on-board ... APIs on Azure Azure APIs On-prem APIs 3rd party APIs

Azure API Management Architecture DEVELOPER PORTAL APP DEVELOPERS PROXY APPS / Consumers BACKEND SERVICES PUBLISHER PORTAL API PUBLISHERS Hosted anywhere. Developed using any technology.

= Azure Active Directory = Azure VNet Browser Clients Mobile Devices = Azure Service Bus = Azure Active Directory = Azure VNet = Azure API Management = Azure Batch = Azure Storage = Azure SQL DB = Azure Search = Azure Worker Role

Solution in action Demo…

Questions?

Thank you!