Microservices with .NET 6 and AWS Tutorial - Part 1

[@WesDoyle]

Welp, I said "monolithic application on the other hand" at 2:45 when I meant to say "microservices architecture on the other hand!" Thanks for watching :)

[@khanfaizan05]

I subscribed without even watching.. knowing that you have something better to offer

[@simplepycodes]

Finally i got a better understanding of this concept. Thanks a lot, appreciate your effort.

[@ryadean]

You're a great guy Wes putting these out for people to learn for free! Enjoyed the first episode, how regularly will you be releasing them? :)

[@WesDoyle]

Hey Ryan, I'll be releasing once every 2 days throughout this series. Thanks for watching!

[@mr.nobody4494]

This series of videos are amazing, some much value. Thanks!

[@PoPo-lt1zd]

Thank you for this series Wes!

[@WesDoyle]

Thanks for watching, Po Po - more to come!

[@jimmydavila7196]

Excellent Tutorial. Thank you Wes

[@2005Azm]

Wonderful! Thank you Wes

[@mehdihadeli]

Great, thanks. Keep going.

[@jinalkumarpatel5138]

Nice video. One question though ..how microservices deal with common data like lookup list that can used by multiple service at the sametime it required locally too when join performed.

[@WesDoyle]

Hi there, this is a great question, and a pretty big topic. There a few strategies to consider. I plan on making a video about this soon. One strategy is to duplicate data across services via pub/sub pattern - this keeps the joining logic within the data layer of a single service. Another approach is to use a composite service responsible for the joins - if joins move to the application layer, latency will surely increase. Another approach is to share a database, have services each use a separate schemas on that database, and create a read for the necessary join as a View in the database layer.

[@jinalkumarpatel5138]

@@WesDoyle Thanks for reply and surely it helps. I am in much favor of pub/sub as it gives true meaning of microservice as separate unit. Second option is like sync call to another service and that is somewhat if possible avoided. Third seems to be a good option. Definitely I am looking forward remaining videos on this microservice series.

[@NicholasIbarra01]

Also would love to see the same code uploaded to azure, just a thought.

[@WesDoyle]

Thanks for the idea, Nicholas!

[@ryanrieben3517]

Me too!

[@kisornanda5848]

Wes, Loving the series. The architecture diagrams look cool. What tool have you used to create the AWS diagram?

[@naeemdeshmukh7035]

Hello Wes, Amazing content! Can you please share github repo link for me to clone this?

[@ipelengmekgwe834]

Great work! Any chance you'll upload this to udemy?

[@alysonramos3424]

Lov u content man

[@VinuP2023]

Wes, +1 for replicating this in Azure please

[@johncraig5979]

It's been a while. I've been on hiatus with coding and learning for a year since 2021 turned into "2020: part II". It's time to get back in that learning groove with a new series I suppose.

[@WesDoyle]

John! Great to hear from you. Hope you're doing well!

[@Nurtylek]

what about microservices on nodejs with aws 😁

hi, i need help here. i couldnt run "dotnet sln new **/*.csproj". how can i run it?

[@RaZziaN1]

Command for windows: dotnet sln add (ls -r **/*.csproj) , if dotnet sln add (ls -r **/*.csproj) does not work for you. (conemu)

[@WesDoyle]

thanks!