Slides for talk bit.ly/rh-shithappens

15. Shit happens
achieve extensibility, modularity and loosely
coupled architecture with events

16. Rafał Hryniewski
@r_hryniewski
fb.me/hryniewskinet
.NET Dev
Blogger
Speaker
Community leader
https://hryniewski.net
rafal@hryniewski.net

18. Shit happens
achieve extensibility, modularity and loosely
coupled architecture with events

19. Agenda
 Event driven architecture 101
 Events in monolith
 Processing events outside of main process
 Events in cloud

21. Systems based on events are
 Loosely coupled
 More modular
 Easier to expand
 Scalable

22. Systems based on events should have
 Events
 Event producers
 Event channel
 Event consumers

24. Defining an event
 Something happened
 It’s somewhat important (you would notify someone about that if you’ve done it
manually)
 Change of state or other action occurred
 It ended successfully

25. Defining an event
An event can be defined as "a significant change in state".
- Wikipedia

26. What’s an event channel?
 Receiving
 Waiting
 Propagation

28. Events can be propagated
 In memory
 Via RabbitMQ, Kafka etc.
 Via cloud services like Azure Service Bus, AWS SNS, GCP Pub/Sub, IBM Event
Streams etc.

29. Messaging 101
 Queueing
 Publish/Subscribe

31. What can consume event?
 Some kind of event consumer class which subscribe for event
 Cloud services like Functions, Lambdas etc.
 Stream analytics platforms like Azure Stream Analytics, Apache Spark etc.
 Event Journal/Data Lake
 BI

35. How it should’ve been done

36. Create abstraction

37. Define our event

38. Define our event

39. Create event bus

40. Define our consumers

41. Define our consumers

43. Publish event

47. Worker process
Event consumer 1
Worker process
Event consumer 2
Event channel

53. Event channels
 Azure – Service Bus, Event Hub, Event Grid
 AWS – SNS
 GCP – Pub/Sub

54. Which one to choose on Azure?

55. Azure Service Bus
 Reliable messaging
 Traditional ESB
 Capable of delivering messages in-order
 Supports topics and subscriptions
 Support at least once delivery

56. Azure Event Hub
 Capable of handling millions of events per second
 Can replay event streams
 Great for collecting telemetry and passing events to analytics platform
 Can handle more data in message

57. Azure Event Grid
 Low cost, serverless solutions for small event notifications
 Supports dead lettering
 Supports publish/subscribe
 Paid per event consumption
 Go to solution for event driven applications

61. bit.ly/rh-shithappens

62. Questions?

63. @r_hryniewskifb.me/hryniewskinet