1 00:00:00,420 --> 00:00:06,120 In this video, we are going to talk about event driven microservices architectures. 2 00:00:07,310 --> 00:00:13,930 Basically advantage of Microsoft's architectures is means communicating with microservices via event 3 00:00:13,970 --> 00:00:14,750 messages. 4 00:00:15,230 --> 00:00:17,780 We said that we wanted an architectures. 5 00:00:17,780 --> 00:00:21,830 We can do asynchronous behavior and lose the coupled services. 6 00:00:22,790 --> 00:00:29,480 In example, instead of sending the request when data needed, services consume them via events. 7 00:00:29,720 --> 00:00:32,330 This provide to performance increases. 8 00:00:33,280 --> 00:00:39,130 But also there are huge innovations on the event driven microservice architectures, like using real 9 00:00:39,130 --> 00:00:44,740 time message platforms, stream processing, even tops, real time processing, batch processing, data, 10 00:00:44,740 --> 00:00:46,060 intelligence and so on. 11 00:00:47,020 --> 00:00:49,900 So let me recap what is event driven architecture? 12 00:00:49,930 --> 00:00:53,860 Basically, we use events when implementing our use cases. 13 00:00:54,010 --> 00:01:00,430 For example, for our E commerce application, we have a few microservices like customer order payment 14 00:01:00,430 --> 00:01:07,580 and products and we have several use cases across microservices like a customer creates an order with 15 00:01:07,600 --> 00:01:12,640 some products and if the payment is successful, the products should be delivered to the customer. 16 00:01:12,910 --> 00:01:14,500 This is one of the use cases, right? 17 00:01:15,490 --> 00:01:21,700 So we can perform the whole process with events and event is more understandable for customers also. 18 00:01:21,970 --> 00:01:27,940 So that could be a flow of events like a customer creates an order, the customer receives a payment 19 00:01:27,940 --> 00:01:28,660 request. 20 00:01:28,900 --> 00:01:33,640 If the payment is successful, the stock is updated and the order is delivered. 21 00:01:33,850 --> 00:01:40,000 If the payment is not successful, roll back the order and set the order status is not completed. 22 00:01:40,540 --> 00:01:46,870 So this is more human readable and if any business requirement appears, it is easier to change the 23 00:01:46,870 --> 00:01:47,440 flow. 24 00:01:50,410 --> 00:01:52,030 This is also a very good match. 25 00:01:52,030 --> 00:01:58,240 The microservices and communications microservices will only care about the events, not about the other 26 00:01:58,240 --> 00:01:59,290 microservices. 27 00:01:59,380 --> 00:02:04,300 They process only events and publish any event to trigger other services. 28 00:02:05,320 --> 00:02:09,190 This approach is traditional approach for event driven architectures. 29 00:02:09,460 --> 00:02:15,020 But we can make this event driven approach is more generic and real time event processing feature. 30 00:02:15,040 --> 00:02:16,960 With evolving this architectures. 31 00:02:17,790 --> 00:02:21,360 There are huge innovations on the Microsoft's architectures. 32 00:02:21,390 --> 00:02:25,980 As we said before, real time message platform, stream processing events, ups and so on. 33 00:02:27,330 --> 00:02:28,740 Please see this image. 34 00:02:28,770 --> 00:02:34,660 According to this live event with Microsoft's architecture, everything is communicating via event. 35 00:02:35,340 --> 00:02:40,800 We Can Think Event Up is a huge event store database that can make real time processing. 36 00:02:41,460 --> 00:02:47,900 As you can see that every microservices, applications, Iot device even function as a service server 37 00:02:47,910 --> 00:02:52,500 services can interact with each other with subscribing events in event hub. 38 00:02:52,980 --> 00:02:56,880 Also, these event upstream data can process by big data. 39 00:02:56,880 --> 00:03:03,360 Tools like Apache Spark also can apply to machine learning pipelines for generating recommendation service 40 00:03:03,360 --> 00:03:07,440 like recommend the best next offer for our ecommerce application. 41 00:03:07,710 --> 00:03:10,570 So this is the event of microservice architecture. 42 00:03:10,770 --> 00:03:15,780 In the next video we will see application integration pattern for microservices.