En esta sesión hablaremos de como modernizar las actuales tecnologías de integración con Logic Apps, la nueva tecnología serverless de Microsoft para el diseño y construcción de flujos de trabajo.
9. ■Implement and orchestrate visually designed integration workflows
■Azure Portal or Visual Studio
■Azure SDK + Azure Logic Apps Visual Studio Tools
■Orchestrate distribute microservices
■Rich ways to process and manipulate data that can be obtained or pushed via different
connectors
■Expose your integrations as microservices
■Enterprise Integration Pack
■Manipulate XML and Flat Files
■B2B Integrations with AS2 and EDI
■100+ Connectors
■Protocols, Hybrid, SaaS, …
Logic Apps
10. Logic Apps Connectors
SaaS Apps and Services Azure and Power Apps
Protocols
Hybrid
B2B, EDI, AS2 and XML
11. ■Pay per Action
■e.g. If you set up a Logic App to poll for data once every minute over the course
of 10 days, that App would generate 14,400 billable actions.
■e.g. If that same Logic App also included 500 workflow steps per day as part of
the daily polling, the Logic App would generate an additional 5,000 billable
actions.
■Don’t worry about resources, only in billable actions
■Don’t worry about VMs, PaaS VMs, … not require infrastructure to be
provisioned
■Don’t worry about the Platform, focus on code, deployment and
managing the App.
Logic Apps and Serverless
12.
13.
14. ■Cloud only
PROS
■Manual, easy to test
CONS
■Can’t share knowledge with others
■Can’t integrate on automatic builds
■Not repeatable and not reliable
Testing the Logic Apps
15. ■Black-box testing
PROS
■Automate test in most scenarios
■Repeatable test
■Can share some knowledge
■Less risk
CONS
■Our Logic Apps has been executed as we expected?
■Test can be broken waiting for different steps
■Some scenarios could be difficult to test
Testing the Logic Apps
16. ■White-box testing
PROS
■Repeatable test
■Provides extensive knowledge
■Low risk
■Test what happens inside Logic App
■Test reliable
■Test actions that you expect that execute
CONS
■Diagnostics (slow, old events)
Testing the Logic Apps
17.
18.
19. Monitoring the Logic Apps
■Activity Logs
■For information about your resource as seen
by the Azure infrastructure.
■The log contains information such as times
when resources are created or destroyed.
■Metrics
■Collectable metrics vary based on the
resource type.
■Performance
■Diagnostics Logs
■Tracking and business data
22. Monitoring the Logic Apps (Diagnostics Logs)
■Save them to a Storage Account
■For auditing or manual inspection.
■Specify the retention time (in days) using
the Diagnostic Settings.
■Stream them to Event Hubs
■For ingestion by a third-party service or
custom analytics solution such as PowerBI.
■Analyze them with OMS Log Analytics
24. Monitoring the Logic Apps (Diagnostics Logs)
■We can search with Tracked Properties (or Business data) values
* Type=AzureDiagnostics status_s=Succeeded trackedProperties_CustomerName_s = Jose
■Only adding the Tracked Properties to our Logic App
