1 00:00:00,510 --> 00:00:05,300 In this video, we are going to talk about benefits of Amazon space. 2 00:00:06,220 --> 00:00:14,080 The first benefit is eliminate administrative overhead, 8 minutes, all ongoing operations and underlying 3 00:00:14,080 --> 00:00:19,210 infrastructure needed to provide a highly available and scalable message service. 4 00:00:20,200 --> 00:00:21,380 With Amazon case. 5 00:00:21,400 --> 00:00:27,610 There is no upfront cost, no need to acquire, install and configure messaging software and no time 6 00:00:27,610 --> 00:00:31,630 consuming build out and maintenance of supporting infrastructure. 7 00:00:32,870 --> 00:00:39,380 Schools are dynamically created and scaled automatically so you can build and grow applications quickly 8 00:00:39,380 --> 00:00:40,520 and efficiently. 9 00:00:42,440 --> 00:00:47,660 The second benefit, we can say that durability for the safety of your message. 10 00:00:47,690 --> 00:00:56,080 Amazon stores them on multiple service standard cues, supports at least one message delivery and five 11 00:00:56,180 --> 00:00:59,270 Q supports exactly one message processing. 12 00:01:00,800 --> 00:01:06,500 And also we can say that the reliability almost on each case logs your message during the processing 13 00:01:06,500 --> 00:01:12,290 so that multiple producers can send and multiple consumers can receive messages at the same time. 14 00:01:14,200 --> 00:01:21,070 Reliable delivered messages use Amazon asks to transmit any volume of data at any level of throughput 15 00:01:21,070 --> 00:01:24,910 without losing message or requiring other services to be available. 16 00:01:25,120 --> 00:01:32,350 So Amazon lets you decouple the application components so that they run and fail independently, increasing 17 00:01:32,350 --> 00:01:34,660 the overall fault tolerance of the system. 18 00:01:35,440 --> 00:01:42,160 Multiple copies of every message are stored redundantly across multiple availability zones so that they 19 00:01:42,310 --> 00:01:44,260 are available whenever they need it. 20 00:01:44,530 --> 00:01:46,960 So we will also use this feature. 21 00:01:46,960 --> 00:01:54,220 When we are designing our ecommerce application, we basically decouple basket and ordering microservices 22 00:01:54,220 --> 00:02:01,330 with using the Amazon event page, but Amazon each publish message and don't store anywhere. 23 00:02:01,330 --> 00:02:03,460 So it is Amazon case. 24 00:02:03,520 --> 00:02:08,620 We decoupled application components and they can run and fail independently. 25 00:02:08,650 --> 00:02:13,240 Even the ordering microservices fail and can consume some message. 26 00:02:13,240 --> 00:02:15,820 These messages are stored in the case. 27 00:02:17,170 --> 00:02:20,230 So another benefit we can say that scalability. 28 00:02:21,710 --> 00:02:28,450 Amazon case can process each buffer request independently, scaling transparently to handle any load 29 00:02:28,450 --> 00:02:31,990 increase or spikes without any provision in production. 30 00:02:33,070 --> 00:02:39,190 So another benefit we can say gain availability almost in this case also uses redundant infrastructure 31 00:02:39,190 --> 00:02:46,030 to provide highly concurrent access to message and high availability for producing and consuming messages. 32 00:02:47,290 --> 00:02:50,170 So scale elastically and cost effectively. 33 00:02:50,200 --> 00:02:57,820 Amazon is leveraging the cloud to dynamically scale based on the demand, as is the case elastically 34 00:02:57,820 --> 00:03:03,790 with your application so you don't have to worry about capacity planning or peer provisioning. 35 00:03:04,610 --> 00:03:10,610 There is no there is no limit to the number of message per queue and standard queues provide nearly 36 00:03:10,610 --> 00:03:11,840 unlimited throughput. 37 00:03:12,170 --> 00:03:18,470 Costs are based on usage which provide significant cost saving versus the always on model of self managed 38 00:03:18,470 --> 00:03:18,950 messaging. 39 00:03:18,950 --> 00:03:19,760 Middle based. 40 00:03:21,700 --> 00:03:24,310 And the lost use case of the benefits. 41 00:03:24,310 --> 00:03:30,910 We can say that security you control who can send message and receive message from the Amazon. 42 00:03:31,390 --> 00:03:39,130 Q We can keep sensitive data secure, and you can use Amazon's case to exchange sensitive data between 43 00:03:39,130 --> 00:03:43,060 applications using server side encryption to encrypt each message. 44 00:03:43,060 --> 00:03:51,280 But the Amazon case SC integration with a key management service allows you to centrally manage the 45 00:03:51,280 --> 00:03:57,520 keys that protect a scarce message, along with the keys that protect your other resources.