1 00:00:00,300 --> 00:00:06,540 In this video, we are going to learn how we can use a lambda as a microservices. 2 00:00:06,780 --> 00:00:12,420 In the last video we understand that lambda function URL feature added to add is in order to adopting 3 00:00:12,420 --> 00:00:13,230 organizations. 4 00:00:13,230 --> 00:00:18,900 Microservice requirements organizations are adopting microservice architecture to breed resilient and 5 00:00:18,900 --> 00:00:21,480 scalable applications using ADA lambda. 6 00:00:21,720 --> 00:00:27,060 These applications are composed of multiple serverless functions that implement the business logic. 7 00:00:27,270 --> 00:00:30,660 So let's evaluate the microservices and a lambda. 8 00:00:30,810 --> 00:00:33,400 Let's remember what are the microservices? 9 00:00:33,420 --> 00:00:39,210 Microservices are small business services that can work together and can be deployed autonomously and 10 00:00:39,210 --> 00:00:40,260 independently. 11 00:00:40,650 --> 00:00:46,080 These services communicate with each other by talking over the network and building many advantage with 12 00:00:46,080 --> 00:00:46,560 them. 13 00:00:46,890 --> 00:00:51,270 One of the biggest advantage is that they can be deployed independently. 14 00:00:51,300 --> 00:00:55,590 Also, it offers the opportunity to work with many different technologies. 15 00:00:55,770 --> 00:01:02,370 So we can say that microservices have their own technology stack, including the database and data management 16 00:01:02,370 --> 00:01:09,360 model communicate to each other over a combination of rest APIs and event streaming and message blockers 17 00:01:09,570 --> 00:01:15,660 and microservices organized by business capability, with the line of separating services often referred 18 00:01:15,660 --> 00:01:17,070 as a bounded context. 19 00:01:18,220 --> 00:01:22,690 So when it comes to a slam dunk, a slam dunk for greater agility. 20 00:01:22,720 --> 00:01:28,300 It is clear that microservices can help companies be more agile and develop software faster. 21 00:01:28,330 --> 00:01:31,600 So where does a slumdog come into the picture? 22 00:01:31,900 --> 00:01:37,660 A place LAMDA is a service that allows you to run your function in the cloud, complete the service, 23 00:01:37,660 --> 00:01:40,270 and eliminates the operational complexity. 24 00:01:40,990 --> 00:01:47,590 You upload your code to the lambda and it takes care of everything needed to run and scale its execution 25 00:01:47,590 --> 00:01:51,110 and fulfill conditions and high availability requirements. 26 00:01:51,130 --> 00:01:56,260 Lambda supports several programming languages so you can choose the most suitable one. 27 00:01:58,520 --> 00:02:00,050 It integrates with the API. 28 00:02:00,050 --> 00:02:06,070 Gateway allows you to invoke functions with the API calls and make your architecture complete the service 29 00:02:06,080 --> 00:02:07,010 serverless. 30 00:02:07,190 --> 00:02:14,600 There are several ways to invoke a function we can invoke by event, or we can invoke another add services 31 00:02:14,600 --> 00:02:21,500 or another application so we can put a number as a microservices in our applications. 32 00:02:21,770 --> 00:02:27,710 You can see the image on the slide that shows the architecture of serverless microservices with a lambda 33 00:02:27,710 --> 00:02:33,230 where the entire service is built from the managed services which removing the architectural overhead 34 00:02:33,260 --> 00:02:39,290 of designing for scaling and high availability and eliminating the operational efforts of operating 35 00:02:39,290 --> 00:02:42,650 and monitoring the microservices underlying infrastructures. 36 00:02:45,070 --> 00:02:50,410 In microservice architecture, each of the application components is decoupled and deployed and run 37 00:02:50,410 --> 00:02:51,380 independently. 38 00:02:51,400 --> 00:02:58,740 An API creates with the Amazon API gateway and then a lambda initiated function is all we need to build 39 00:02:58,750 --> 00:02:59,800 as a microservices. 40 00:03:00,820 --> 00:03:07,780 Team can use these services to decouple and segment your environment to the desired level of details. 41 00:03:08,290 --> 00:03:15,700 In general, in general, a microservice environment can introduce any difficulties, for example, 42 00:03:15,700 --> 00:03:23,650 repeated overhead for create each new microservices and also problem optimising server density and usage 43 00:03:23,890 --> 00:03:29,740 and complexity of running multiple versions of multiple Microsofts at the same time, and client side 44 00:03:29,740 --> 00:03:32,440 code requirements to integrate with many services. 45 00:03:32,470 --> 00:03:38,620 When you create microservices using serverless resources, these problems become less difficult to resolve 46 00:03:38,620 --> 00:03:40,990 and in some cases simply disappear. 47 00:03:42,190 --> 00:03:48,370 So the serverless microservice pattern reduces the barrier for the creation of each subsequent microservices 48 00:03:48,610 --> 00:03:55,090 API gateway, even allow for the cloning the existing APIs and using the lambda functions in other accounts. 49 00:03:55,120 --> 00:03:59,110 Optimizing server utilization is no longer relevant with this pattern. 50 00:03:59,320 --> 00:04:05,340 Finally, Amazon API Gateway provides the programmatically generates the client case that are programmatically 51 00:04:05,620 --> 00:04:09,820 a number of popular languages in order to reduce the integration overhead. 52 00:04:10,120 --> 00:04:15,550 We can see the image on the slide that shows the architecture of serverless microservices with using 53 00:04:15,550 --> 00:04:17,770 Amazon API Gateway and a Lambda. 54 00:04:17,770 --> 00:04:23,350 So API Gateway API is proxy to individual microservices backed by the lambda functions. 55 00:04:23,380 --> 00:04:26,500 You can see the microservices one, two, three and four. 56 00:04:26,530 --> 00:04:34,150 That proxy by the ADA is Amazon API Gateway and all the microservices handled with the ADA Lambda functions. 57 00:04:34,780 --> 00:04:40,660 So as you can see that we have understood that we can use a lambda as a microservices in serverless 58 00:04:40,660 --> 00:04:47,410 architecture and we understood that the importance of the function URLs in a lambda as a microservices.