1. Build Micro Service landscape with Azure Functions
Mattias Lögdberg

2. Mattias Lögdberg Solution Architect Azure Specialist Microsoft MVP
MLogdberg

3. Building a micro service landscape
Small components
Scaling
Throttling (even out workloads)
Events
Create a facade

4. Mono-lithic application Inside client app Complex framework
Outside client app
Micro- functionality
Loosely coupled components

5. Learn the icons

12. Scenario based, requirements
Recieve data via HTTPS
Store data
Provide API for external consumers
Detect updates and provide change feed to other systems (pub/sub)
Keep track of what is happening

13. Scenario
Drawing time

14. Some context

15. Bindings Standard functionality Smaller and more focused Functions
Less code

16. Scaling On instance level (server)
On thread level (threads per instance)

17. Lets start!
put /product/{id}

18. Monitoring Scaling Errors Performance Live Stream
Lets’ watch how this goes (runner)

19. All good?
Load test

20. Monitoring
End to End
Lets’ watch how this goes (runner)

21. Lets add an API
get /product/{productnumber}
put/product/{id}

22. Update Events in Cosmos

23. Custom Bindings / Extensions
Event Grid

24. Lets add Update Event’s
get /product/{productnumber}
put /product/{id}

25. Reflection
get /product/{productnumber}
put/product/{id}

26. Mono-lithic application Inside client app Complex framework
Outside client app
Micro- functionality
Loosely coupled components

27. Lessons learned Design is important
Security on end user is often important when used with mobile apps
Facade’s help remodel, handle change is key to success
Micro Service landscape boost innovation
Good CI/CD story helps for change and rapid development
For End To End tracking use same Application Insights
Problem deploying? Due to locked files
MSDEPLOY_RENAME_LOCKED_FILES=1

28. Questions?

29. Thanks! Mattias Lögdberg, Solution Architect