Session co-presented with Tharanga Chandrasekara (Business Solution MVP) at Directions ASIA 2019 Reactive or event driven programming allow systems to have access to the correct data at the correct time. By using a BC extension and the AL language in conjunction with Azure Event Grid, you can benefit from this powerful publisher/subscriber engine to notify systems of changes in your data – as they happen - so you can enable faster business processes across your enterprise. In this session Tharanga Chandrasekara (Business Solutions MVP) and Wagner Silveira (Azure MVP) will show you how to implement a generic extension that allows you to publish events into Azure Event Grid, and how you can use Azure Integration Services to subscribe to those events and take action.

1. w w w . d i r e c t i o n s a s i a . c o m
The Dynamics SMB Focused Partner Community

2. Exploring Azure Integration Services –
Unlocking new integration potential for
D365 BC with Azure Event Grids
www.directionsasia.com
Tharanga Chandrasekara
Wagner Silveira

3. Tharanga Chandrasekara
Theta Senior Consultant – ERP
Microsoft Business Solutions MVP
Theta is a NZ-owned IT consultancy with offices in Auckland, Wellington and Christchurch. Our
team of more than 200 experienced professionals help organisations like yours – in New Zealand
and around the world – to transform their businesses with technology.
Wagner Silveira
Principal Integration Architect – Digital
Microsoft Azure MVP

4. Introduction to Reactive Programming
Azure Event Grids
Hands On
Design Considerations
Takeaways
Agenda

5. Keeping systems in Sync
• A common integration problem
• Multiple patterns
• Poll
• Push
• Some examples

6. Polling Challenges
• Eventual consistency
• Polling time sweet spot
• Can drain resources

7. Push Challenges
• Onus on source to keep systems up-to-
date
• Integration must understand all
downstream systems
• Can become very complex

8. What is a better
solution?
• A brokered event system
• Source publish to broker
• Interested parties subscribe to
broker
• Decouples publishing to
subscribing processes
• Introduces a new player – the
pub/sub broker

9. Introducing Azure Event Grid
• Simplify event-based app
development with a publish-
subscribe model
• Simple HTTP-based event
delivery
• Build better, more reliable
applications through
reactive programming
• Focus on product
innovation

10. MICROSOFT CONFIDENTIAL – INTERNAL ONLY
Event Grid
Concepts
• Events: what happened
• Event Publishers: where
it took place
• Topics: where publishers
send events
• Event Subscriptions: how
you receive events
• Event Handlers: the app
or service reacting to the
event

11. What is an Event?

15. First Approach
Event Happen in
Business Central
Push Event
Details to a Table
Allow to Access
through API

16. Challenges Faced
Rapid growth of
the database size
DeadlocksToo many API
requests
Increase of Security
Threats

17. Second Approach
Event Happen in
Business Central
Push Event Details
to a Azure Event
Grid

18. Advantages
Extendable Easy to Manage High Security Once off
Development

19. Hands on Scenarios
• Customer Credit Limit Updated
• Sales Order Released

20. Design considerations
• Follow the event core concepts
• Define the event triggers
• Generic (CRUD)
• Status changes
• How much data is enough?
• Think about the Event Grid limits
• How to “re-hydrate” records
• API access
• Claim check pattern

21. Takeaways
• Event grids decouples event
publishing from handlers
• Enables real time scenarios
• Easy extensibility in BC to support it
• Think about the types of event to
publish
• Think about the data strategy