1 00:00:00,150 --> 00:00:02,910 ‫So now let's talk about Amazon MQ. 2 00:00:02,910 --> 00:00:05,340 ‫So we know about SQS and SNS 3 00:00:05,340 --> 00:00:07,080 ‫and they're cloud-native services 4 00:00:07,080 --> 00:00:10,980 ‫because they are proprietary protocols from AWS. 5 00:00:10,980 --> 00:00:13,590 ‫They use their own sets of APIs. 6 00:00:13,590 --> 00:00:17,340 ‫But if you are running traditional application on-premises, 7 00:00:17,340 --> 00:00:19,320 ‫you may use open protocols 8 00:00:19,320 --> 00:00:24,320 ‫such as MQTT, AMQP, STOMP, Openwire, WSS. 9 00:00:25,530 --> 00:00:28,410 ‫And when you're migrating your application to the cloud, 10 00:00:28,410 --> 00:00:31,530 ‫you may not want to re-engineer your application 11 00:00:31,530 --> 00:00:35,910 ‫to use the SQS and the SNS protocols or APIs. 12 00:00:35,910 --> 00:00:39,090 ‫So instead, you wanna use the traditional protocols 13 00:00:39,090 --> 00:00:42,330 ‫you used to, such as MQTT, AMQP, and so on. 14 00:00:42,330 --> 00:00:44,850 ‫So for this, we can use Amazon MQ. 15 00:00:44,850 --> 00:00:46,830 ‫So Amazon MQ is very simple. 16 00:00:46,830 --> 00:00:51,210 ‫It's a managed message broker service for two technologies, 17 00:00:51,210 --> 00:00:54,090 ‫for RabbitMQ and for ActiveMQ. 18 00:00:54,090 --> 00:00:57,030 ‫So RabbitMQ and ActiveMQ are, for example, 19 00:00:57,030 --> 00:01:00,390 ‫on-premises technologies that provide you access 20 00:01:00,390 --> 00:01:03,060 ‫to the open protocols I just mentioned. 21 00:01:03,060 --> 00:01:06,330 ‫So then we can get a managed version of these brokers 22 00:01:06,330 --> 00:01:08,850 ‫onto the cloud thanks to Amazon MQ. 23 00:01:08,850 --> 00:01:11,310 ‫So as such, you can understand the implications. 24 00:01:11,310 --> 00:01:15,630 ‫First of all, Amazon MQ doesn't scale as much as SQS or SNS, 25 00:01:15,630 --> 00:01:18,540 ‫which have sort of like infinite scaling. 26 00:01:18,540 --> 00:01:20,550 ‫And because Amazon MQ runs on servers, 27 00:01:20,550 --> 00:01:22,410 ‫you may have server issues. 28 00:01:22,410 --> 00:01:24,960 ‫And so you can run multi-AZ setup 29 00:01:24,960 --> 00:01:28,350 ‫with a failover if you want to be highly available. 30 00:01:28,350 --> 00:01:31,830 ‫Also, Amazon MQ comes with both a queue feature, 31 00:01:31,830 --> 00:01:33,900 ‫so it looks like SQS, 32 00:01:33,900 --> 00:01:36,510 ‫and topic features, it looks like SNS 33 00:01:36,510 --> 00:01:38,733 ‫as part of a single broker. 34 00:01:39,660 --> 00:01:43,290 ‫So Amazon MQ is going to be used only and only if 35 00:01:43,290 --> 00:01:45,810 ‫a company is migrating to the cloud 36 00:01:45,810 --> 00:01:48,330 ‫and needs to use one of these open protocols, 37 00:01:48,330 --> 00:01:51,480 ‫such as MQTT, AMQP, STOMP, et cetera, et cetera. 38 00:01:51,480 --> 00:01:53,940 ‫Otherwise, it should be using SQS and SNS 39 00:01:53,940 --> 00:01:55,560 ‫because they scale a lot better 40 00:01:55,560 --> 00:01:56,940 ‫and they're way more integrated 41 00:01:56,940 --> 00:02:00,090 ‫with Amazon Web Services than Amazon MQ. 42 00:02:00,090 --> 00:02:03,090 ‫So I hope that helps and I will see you in the next lecture.