1
00:00:00,350 --> 00:00:01,580
‫So just a quick lecture

2
00:00:01,580 --> 00:00:03,590
‫on a Microservice Architecture

3
00:00:03,590 --> 00:00:05,930
‫you can implement with API gateway.

4
00:00:05,930 --> 00:00:07,010
‫So thanks to API gateway.

5
00:00:07,010 --> 00:00:08,290
‫You can have a single interface

6
00:00:08,290 --> 00:00:11,020
‫for all the microservices in your company,

7
00:00:11,020 --> 00:00:12,410
‫and you can use API endpoints

8
00:00:12,410 --> 00:00:13,800
‫with various resources in the backends.

9
00:00:13,800 --> 00:00:16,300
‫So, you can hide the complexity for your clients.

10
00:00:16,300 --> 00:00:17,750
‫So to say, we have an API gateway

11
00:00:17,750 --> 00:00:20,200
‫and we have a /service1 route,

12
00:00:20,200 --> 00:00:23,300
‫which sends it to a elastic load balancer,

13
00:00:23,300 --> 00:00:27,160
‫which is backing an actual ECS cluster of microservices.

14
00:00:27,160 --> 00:00:30,240
‫Or we can have /docs to send an S3 buckets

15
00:00:30,240 --> 00:00:31,630
‫that contain some study content.

16
00:00:31,630 --> 00:00:34,010
‫For example, the documentation of your service,

17
00:00:34,010 --> 00:00:36,940
‫or /service2 to have an ELB connected

18
00:00:36,940 --> 00:00:38,932
‫to an Amazon EC2 Auto Scaling group fleets.

19
00:00:38,932 --> 00:00:43,090
‫Okay? So all these things allow you to define these routes

20
00:00:43,090 --> 00:00:46,730
‫and use the API gateway as a single URL

21
00:00:46,730 --> 00:00:48,890
‫to connect to these services.

22
00:00:48,890 --> 00:00:51,790
‫Then we can use route 53 to register a domain,

23
00:00:51,790 --> 00:00:54,030
‫instead of the DNS for API gateway.

24
00:00:54,030 --> 00:00:57,950
‫Which also allows us to give us some custom addresses

25
00:00:57,950 --> 00:00:59,030
‫based on the client we have to.

26
00:00:59,030 --> 00:01:02,550
‫So, customer1.example.com for one of the clients,

27
00:01:02,550 --> 00:01:06,350
‫or customer2.example.com for a second clients.

28
00:01:06,350 --> 00:01:10,440
‫And we can apply SSL certificates based on these domains.

29
00:01:10,440 --> 00:01:12,630
‫And we can also within the API gateway,

30
00:01:12,630 --> 00:01:14,820
‫apply forwarding and transformation rules,

31
00:01:14,820 --> 00:01:17,160
‫to modify the incoming data

32
00:01:17,160 --> 00:01:19,220
‫before sending into the backends.

33
00:01:19,220 --> 00:01:20,390
‫So I'm showing you this slide,

34
00:01:20,390 --> 00:01:22,590
‫to just show you the kind of architecture

35
00:01:22,590 --> 00:01:25,000
‫that you can implement with API gateway.

36
00:01:25,000 --> 00:01:27,750
‫The idea is that you want to unify your microservices

37
00:01:27,750 --> 00:01:30,820
‫and give an external unified URL.

38
00:01:30,820 --> 00:01:34,540
‫While hiding all the complexity of, routing to a service.

39
00:01:34,540 --> 00:01:38,260
‫Transforming the data and specifying SSL certificates.

40
00:01:38,260 --> 00:01:40,850
‫All of this is done at the API gateway level.

41
00:01:40,850 --> 00:01:42,080
‫So I hope that is helpful.

42
00:01:42,080 --> 00:01:43,980
‫And I will see you in the next lecture