Spring Boot MicroServices Tutorial : API Gateway using Spring Cloud Gateway

Join this channel to get access to the perks:

#sivalabs #java #spring #springboot #springcloud #microservices #restapi #rabbitmq #testing #junit #junit5 #maven #testcontainers #docker #kubernetes

In this video, you will learn:
► How to implement API Gateway using Spring Cloud Gateway
► Understanding CORS (Cross Origin Resource Sharing)
► How to create aggregated Swagger Documentation

❤️ Thanks for watching

References
=============================================

Connect with Me
=============================================

Must Watch Videos
=============================================

Popular Series Playlists
=============================================

⭐ Tags ⭐
best spring tutorials, best spring boot tutorials, how to learn spring boot, mastering spring boot, complete java testing course, java testing best practices, how to build spring boot rest API, spring cloud tutorials, spring boot docker tutorial, spring boot kubernetes tutorial, how to become proficient in java, how to learn spring boot quickly, how to learn spring boot in-depth

[praveens]

I think it's highly unlike that organisations build api gateway programmatically. There are bullet proof API gateway products out there which serves the same purpose with fraction of operating cost and with some rich features.

[VenkateshCh-vyef]

Fetch error
Not Found /v3/api-docs/first
iam getting this error after trying to access the swagger how can i resolve this error

[shreyojitdas]

Sir which playlist should I refer to know springboot and everything related to it?

[TheDummyHead]

I was curious what was the difference between Gateway and Reactive Gateway. The Reactive Gateway was developed first using the project Reactor and WebFlux. It's has more features at the moment. Gateway is built on classical MVC Servlets, but at the moment it lacks many features from the Reactive Gateway. I'm very curious to see if the new MVC Gateway gets more popular.

[TheDummyHead]

I noticed that when using Swagger UI in api-gateway the services URLs bypass the gateway and expose the individual services URL. Is there some way to rewrite it to point back to the generated endpoints from api-gateway? For example if in Swagger UI I select catalog in dropdown, then it shows localhost:8081 as server, which is correct, but won't be reachable from the outside. Correct one would be localhost:8989/catalog in this case.