14. A A A
SOAP Adapter
EDIfact Adapter
REST Adapter
A
AMQP Adapter
SERVICE
Ports are logical artefacts.
Adapters are physical
implementation of ports.
Twilio
FTP
Service Layer
App Layer
19. az login
az group create --name RG-COLLAB --location westeurope
az storage account create --name eucollabstorage --location westeurope --resource-group RG-COLLAB --sku
Standard_LRS
az appservice plan create --name CollabAppServicePlan --resource-group RG-COLLAB --sku B1 --is-linux
az functionapp create --name azcollabfunc --storage-account eucollabstorage --resource-group RG-COLLAB --plan
CollabAppServicePlan --deployment-container-image-name damir.azurecr.io/mydockerimage:v1.0.0
az group delete --name RG-COLLAB
20. az container create --resource-group RG-COLLAB
--name mycollabfunc
--image damir.azurecr.io/mywebapi:latest
--ip-address public --ports 80
--os-type windows
--registry-login-server ***.azurecr.io
--registry-username username --registry-password ***
az container attach --resource-group RG-COLLAB --name mycollabfunc
az group delete --name RG-COLLAB
21.
22.
23. Service Purpose
Service Bus Used for integration scenarios.
Supports many integration patterns and reliable messaging.
Web Service API style ‘MESSAGE’
Relays Used for integration scenarios with NAT
WebService API style RPC through broker.
EventGrid Higher level messaging.
Topic Subscription Management
EventHub Event Streaming
IotHub Event Streaming for telemetry events
Support for twins, commands, device management etc.
27. System-1
System-2
tenant1
System-3
T
Every system uses ‚T‘ as
event receiver, which
defines send-channel.
S3
S2
S1
S21
dst
T2
dst
System-2
tenant2
Autoforwarding
No processing
(mapping) required
T3
dst
S22
dst
S3
dst
Monitor
M
M
M
Mapping/Processing