Protect Your Microservices with Spring Cloud Gateway
HTML-код
- Опубликовано: 7 дек 2022
- Microservice architectures simplify the individual components that comprise our applications, but they introduce new complexity in managing a high number of distributed APIs. With so many moving parts, how can you provide a simplified experience for consumers and ensure that your system is resilient and secure?
Centralized gateways have been a long-standing solution for managing APIs, but microservices demand a new generation of lightweight micro-gateway applications. Spring Cloud Gateway is one such solution. It provides a simple yet flexible API to add the routing, resilience, and control you need to protect the edge layer of your applications. Built on Spring WebFlux, it also ensures an inherently nonblocking mechanism for efficiently routing and manipulating requests.
In this talk, we'll review the motivation for Spring Cloud Gateway and demonstrate a variety of features, such as weighted routing, circuit breakers, rate limiters, and more.
#SpringOneTour2022 #microservices #springboot #springcloud 
Наука
Its really good presentation and speech. Live coding generally its wired experience, live coding on Spring One is mind blowing. Well done
Incredible demo, thanks for sharing.
This is just amazing!
Its powerful i am using it for prod now 🤗
Very Good Demo. @Spring Team, can you please include a link to this video in Cloud Gateway's reference docs.
Also, for the next demo, if you can include an example of OIDC authentication with cloud gateway, that will be great.
just know this gateway things such a wonderful way
Awesome stuff as always;
off-topic: I would like to buy the t-shirt the girl is wearing, please tell me there's a link to buy it
Nice presentation.
nice presentator
Can you provide me repository link for this demo?
which http command line tool is she using ?
httpie
Hi,
May i know what is the purpose of the -Host under predicate? why we need host ? why we are passing as parameter while hitting from client?
Host is just another tool you can use, not mandatory, and its use deppends on your use case. Keep in mind 'predicates' define what route will be applied (first one to match all predicates is selected). Typical examples only use Path which allows you to configure the filters based on the destination, but adding Host is interesting since it would allow you to apply different filters based on the client origin. You could distinguish for instance traffic comming from within or without your datacenter, but this is just a example from top of my mind. The official docs list all predicates available if you are curious about all possibilities.
@@abelsalgadoromero4402 "apply different filters based on the client origin", I believe it's based on the request destination instead. Imagine your gateway proxies some systems hosted on different domains.
@@abelsalgadoromero4402 nice explanation . it really make sense.
CORS is holding my family hostage please help