Thanks Less , your tutorials are amazing , I just enjoy and love to watching them till the end. I loved it. I would like to ask you if it is possible make another tutorial for your next videos and secure these two microservices with a single Auth service and maybe I ask too much but if you also include roles and permissions in it , then it would be great.
Great tutorial Les..... would be great if you show how to deploy this as production environment in any cloud platform. That would complete any full stack development. Thanks again.
Thank you Les for another amazing tutorial during our lockdown in Melbourne. I'm currently investigating Ocelot for the API gateway and you have given me another option to think about it.
Hi Ray, yeah the Microsoft eShopOnContainers reference architecture that I mention in the video originally used Ocelot, (I've not personally used it), but they then switched to Envoy, (not sure why but it does seem to be gaining ground). Anyway thanks for the feedback and I hope your lock-down is going ok! Cheers, Les
Really helpful video - thank you. If you ever get chance, it would be great to compare how to use Envoy as a sidecar proxy, rather than as a front proxy. A lot of the available resources on the web are pretty impenetrable, so it's a topic that would really benefit from your clear presentations!
Great Video!! I agree that the Envoy documentation looks pretty thorough but I find that I often get lost, bump into dead ends and/or get frustrated with the final definitions. So your video went a long way towards helping me understand a envoy.ymal file that I have to modify! Looking forward to implementing what I’ve learned!!
4 года назад
Thank you, Les. Another great video. Greetings from Serbia.
You are my mentor from the beginning. 😎 I really appreciate your work . Can I get ML.Net based some tutorials too from you.. as they way you make things so easy it's just amazing. Thanks for everything.. ⛱️ Take care
Hello Sir really happy to see the videos, thanks for all your efforts. I have a request can you make video on best practices /architecture/design patterns if possible?
Les, Thank you very much for a fantastic content.I was looking for this for quite sometime, my tea cluster is showing 'no healthy upstream' i am not sure why, need to investigate, what i have done wrong! YAML is giving tough time!
Very good explanation. A bit difficult to follow especially when come to the point of constructing the envoy.yaml file. Lucky you have provide all the repo files on the GitHub. We must very careful the space in the envoy.yaml file. Most of the error happened due to the spacing. Well, thank you very much. Really appreciate it. By the way, I hope you can have a session for NGINX.
1 thumb up just to cover this topic, just found you, 1 thumb up for this detail and this intro, 1 thumb up for all your videos, 1 thumb up for your nice manner, 1 thumb up for the lenght of the video, 1 thumb up for your time codes , i have more thumbs all for you!!
Absolutely fantastic tutorial (along with all your other tutorials!). I love the way you present the content, very informative and descriptive. In this tutorial, I think things have changed with the Envoy documentation as I was unable to find the original envoy.yaml file you used. Of course, I was able to grab a copy from your GitHub page, however it was the 'final' version. I had to go through the yaml file section of the video several times to clean out all the upcoming content. As a recommendation, it may be helpful in future videos if you could include some of the 'starting point' code in cases where you are cutting and pasting. Even after I stripped out and reverted your 'final code' back to 'original code' as best I could, I ran into an 'Invalid path: /etc/ssl/certs/https.crt' error when trying to start up the Envoy container (so I am guessing I still missed something). Otherwise, I absolutely loved the tutorial, and look forward to learning much more from your channel. Thank you!
Great tutorial, I have learned so much today. I have a question, If I have two services running on / how would one configure envoy to mount these on different path prefixes like /service1 and /service2 ?
envoy... onvoy... dayta.... darta.... meh. I interchange and I haven't worked out why... AND - just watching flights land in Sydney from Melbourne - I'm a little more emotional about it than I thought I would be! Welcome back! Hope you survived the last few months ok.
It would be great if you could create another video about smth. from front-end freamwork - for example Angular. I saw in one of your video that you have extension for that, so maybe couse you're familiar with that. I mean not big deal, just simple communication between api and webpage with security stuff etc. Consider that :) and like always very good material, thank you for your job.
Hi Les, Thanks for this amazing video, I have question or I would say confusion as at last of the video you told about envoy service mesh, I can understand service mesh is for internal traffic and API gateway is for external but my question is can we use both together , what is best practices for this? My another question is for Authentication part, if I can configure authentication on envoy? if yes again whether it should be at service mesh or at gateway? Thanks for all your handwork, I enjoyed watching your video. whenever you get a chance please clarify my doubt. Thanks
Hi Les, request you to re-make or update the video with latest version of .Net Core and envoy. I have been trying since days but unable to configure project on SSL (localhost)
Hi Les, Thanks for Nice and amazing Tutorials. At this lesion , use of envoyproxy as API-Gateway is wonderful. I am thinking on can we replacing "envoyproxy " by "Azure-API mgmt " services and do the same task(URL base routing) ? Thanks,
Thanks for excellent videos. I have a query related to the architecture at 7:50 timeline. If I want to add load balancer to scale microservices then do I have to add load balancer between api gateway and microservices. So api gateway would route request to load balancer and load balancer would distribute the request to microservice api.
I have small change in api gateway is my services like Flights api so i have to consume all apis in same time then entry point of access flight is api gateway so how can achieve this with api gateway? Thanks for video
Not wanting to rain on the party, great tutorial, etc BUT I still have no idea why would anyone want to use Envoy, as opposed to, for example, just nginx or IIS as a reverse proxy ? Please explain what is the benefit / use case ?
Thanks for the tutorial, it's very helpful. How come it's not possible to route towards one's localhost ? And is there a way to solve this aside from using Docker compose ?
I have a question on how you figured out the names for the secrets? How did you know that the key was "Kestrel:Development:Certificates:Password"? People often brush over the small things, but this is an area that I find difficult. All these magic strings that you have to know in order to get things working ...
Thank you very much Les for this great tutorial and explanation of API gateways! I really would be interested in using free automatically refreshing letsencrypt certificates with Envoy. But it seams that this is not an easy task. Maybe its possible with "SDS". What do you think?
Can you use Envoy when your API is GraphQL? probably not since there's only one endpoint and you need to route it according to what's in the body. Is there an alternative? or do you just create your own gateway with stiching\merging?
@@zulhishamtan4308 I've done that and no luck. Manage to get it working by manually installing the cert using this commands: dotnet dev-certs https -ep %USERPROFILE%\.aspnet\https\aspnetapp.pfx -p { password here } dotnet dev-certs https --trust Then importing it to the correct certs folder
Super video, just the stack that I have been trying to learn. Question: At 45:23 your docker-compose file, has the ports mapped for the Coffee API ports: - "8080:80" - "8081:443" However internally, the Coffee Api has the following launch settings in launchSettings.json : { ... "applicationUrl": "localhost:5001;localhost:5000", ... } I was just wondering why the the docker compose file did not reference the 5001 and 5000 ports - if these are internal? Thanks Craig