1 00:00:00,180 --> 00:00:05,340 In this video, we are going to learn what is Amazon API Gateway? 2 00:00:05,910 --> 00:00:09,420 Amazon API Gateway is fully managed service. 3 00:00:09,420 --> 00:00:16,650 That makes it easy for developers to create, publish, maintain, monitor and secure APIs at any scale. 4 00:00:17,220 --> 00:00:23,370 APIs act as a front door for applications to access data, business logic or functionality from your 5 00:00:23,370 --> 00:00:24,480 backend services. 6 00:00:24,600 --> 00:00:31,350 Using Amazon API Gateway, we can create restful APIs and web socket APIs that enable real time two 7 00:00:31,350 --> 00:00:33,060 way communication applications. 8 00:00:33,480 --> 00:00:38,970 API Gateway also supports containerized and serverless workflows as well as web applications. 9 00:00:39,450 --> 00:00:44,370 So we can say that Amazon API Gateway is an ideal service for creating, publishing, maintaining, 10 00:00:44,370 --> 00:00:51,480 maintaining and securing rest HTTP and web socket APIs so we can create, deploy and manage restful 11 00:00:51,480 --> 00:00:58,530 APIs in order to expose backend HTTP endpoints, add some functions or other services. 12 00:00:59,160 --> 00:01:05,850 API developers can create APIs that access ADA or other Web services, as well as a data source in the 13 00:01:06,360 --> 00:01:06,990 cloud. 14 00:01:07,530 --> 00:01:14,880 As an API Gateway API developer, we can create APIs for use in our own client applications, or you 15 00:01:14,880 --> 00:01:18,870 can create your APIs available for the third party applications. 16 00:01:19,980 --> 00:01:23,430 There are two main types of APIs in Amazon API Gateway. 17 00:01:23,520 --> 00:01:29,890 The first one is the restful APIs for building this APIs optimized for serverless workflows and HTTP 18 00:01:29,890 --> 00:01:37,020 backends using HTTP APIs in Amazon API Gateway, we can create again to type rest APIs. 19 00:01:37,020 --> 00:01:39,660 So Rest API divided instead of the two type. 20 00:01:39,660 --> 00:01:44,430 Again, the first one is the HTTP API and the second one is the rest API. 21 00:01:44,910 --> 00:01:50,970 HTTP API are the best choice for building APIs that only require API proxy function functionality. 22 00:01:51,060 --> 00:01:59,430 We come with low latency and cost efficiency rest API with built in features for, for example, OCD 23 00:01:59,430 --> 00:02:01,680 and all to a native core support. 24 00:02:02,010 --> 00:02:04,350 And we have also raised API. 25 00:02:04,410 --> 00:02:05,820 The name can be confusing. 26 00:02:05,820 --> 00:02:13,020 I will explain when we see in the measurement console, but you can understand the definitions. 27 00:02:13,020 --> 00:02:21,840 We have two API types, http API and rest API and in the rest API, if your API require API proxy functionality 28 00:02:21,840 --> 00:02:27,390 and API management feature in a single solution API gateway also offers rest API. 29 00:02:27,420 --> 00:02:33,630 We can develop a rest API where we gain complete control over the request and response along with API 30 00:02:33,630 --> 00:02:34,920 management capabilities. 31 00:02:35,490 --> 00:02:38,700 And the last API type is web socket API. 32 00:02:39,950 --> 00:02:45,830 We can build real time two way communication application such as chat application and streaming dashboards 33 00:02:45,830 --> 00:02:47,390 with the web socket APIs. 34 00:02:47,750 --> 00:02:54,080 API Gateway maintains a persistent connection to handle message transfer between vacant services and 35 00:02:54,080 --> 00:02:55,370 our client applications. 36 00:02:55,370 --> 00:03:02,660 So API Gateway able to create web socket API, we will learn unpack this all types of APIs during the 37 00:03:02,660 --> 00:03:10,670 course, but mostly we will use RESTful APIs capabilities because API gateway creates restful APIs that 38 00:03:10,670 --> 00:03:15,020 are HTTP based and enable stateless client server communication. 39 00:03:15,020 --> 00:03:21,230 And we can implement standard HTTP methods like get post, put patch and delete exit methods. 40 00:03:21,230 --> 00:03:27,030 So we will mainly use API gateway for exposing our microservice APIs to the client applications and 41 00:03:27,030 --> 00:03:28,070 the microservices.