1
00:00:00,360 --> 00:00:07,920
In this section we are going to do hands on lap wielding graceful microservices with a Lambda API Gateway

2
00:00:07,920 --> 00:00:11,370
and Dynamo DB using the ADA place management console.

3
00:00:12,120 --> 00:00:19,050
So in this video we will give all real information about the RESTful Microservices with a Lambda API

4
00:00:19,050 --> 00:00:21,030
Gateway and Dynamo DB table.

5
00:00:21,150 --> 00:00:27,420
As you remember that we have already done and implement these restful microservices without Dynamo DB

6
00:00:27,420 --> 00:00:33,000
in the previous sections, but in this section we will add the Dynamo DB and integrate the Dynamo DB

7
00:00:33,000 --> 00:00:35,700
from the Lambda function and expose the API gateway.

8
00:00:36,240 --> 00:00:37,890
Then we link a microservices.

9
00:00:37,890 --> 00:00:43,500
You are thinking about how a business context can be delivered as a reusable for our consumers.

10
00:00:43,500 --> 00:00:50,760
So that means we are going to create a serverless API that creates, reads, updates and deletes items

11
00:00:50,760 --> 00:00:52,410
from a Dynamo DB table.

12
00:00:52,560 --> 00:00:58,890
Dynamo DB is a fully managed NoSQL database that provides fast and predictable performance with seamless

13
00:00:58,890 --> 00:00:59,790
scalability.

14
00:00:59,820 --> 00:01:06,450
This section takes approximately 20 minutes to complete, and you can do it with a three tier account.

15
00:01:06,480 --> 00:01:11,190
First of all, we will create a Dynamo DB table using the management console.

16
00:01:11,250 --> 00:01:17,100
After that, we create a lambda function using the console, and after that we create a rest API using

17
00:01:17,130 --> 00:01:18,690
the API gateway console.

18
00:01:18,690 --> 00:01:24,570
And lastly, we will test our end to end architecture that you can see on the image of the slide.

19
00:01:24,600 --> 00:01:28,020
This is the reference architecture for restful microservices.

20
00:01:28,020 --> 00:01:33,330
So basically client centered request or microservices by making HTTP calls.

21
00:01:33,360 --> 00:01:39,360
Ideally, our client should have a tight demand to services contract to our API in order to achieve

22
00:01:39,360 --> 00:01:42,960
consistent expectation of microservices possibility.

23
00:01:43,350 --> 00:01:49,740
And after that Amazon API gateway host restful HTTP request and response to the customer.

24
00:01:49,800 --> 00:01:57,090
In this case, API Gateway provides built in authorization, throttling security filters and so on.

25
00:01:57,090 --> 00:01:59,940
So that means we will use rest APIs.

26
00:02:00,060 --> 00:02:05,370
And after that, a list lambda contains the business logic to process incoming API calls and leverage

27
00:02:05,370 --> 00:02:07,680
dynamic DB as a persistent storage.

28
00:02:08,340 --> 00:02:13,620
So Amazon Dynamic DB persistently stores microservices data and scales based on demand.

29
00:02:13,650 --> 00:02:19,710
Since microservices are often designed to be one thing, well, a seamless, more secure data store

30
00:02:19,740 --> 00:02:23,070
is very huge effect for our architectures.

31
00:02:23,460 --> 00:02:29,490
So when we invoke our API, gateway API, API, gateway rusts, request to Lambda function and Lambda

32
00:02:29,490 --> 00:02:35,220
function interacts with the Dynamo DB and return a response to the API Gateway and API Gateway returns

33
00:02:35,220 --> 00:02:37,050
to response to our client application.