Microservice Architecture with ASP.NET Core

[@asiankidschannel]

tried it! at last it is working on my machine! great job Cesar

[@CoopmanGreg]

In your description where you place the times for each section, they do not link to that part of your video. Instead of "•[T01:06] " , I think if you place a space before the 0 and after the 6, it will create an active link, like •[ T01:06 ]

[@defenestratedalien1448]

Really great talk. Wonderful content. Just watching this seriously improved my conceptual understanding of microservices. Not to the interesting and time consuming part; writing code.

[@anatoliysiryi305]

That moment when James Hetfield asking about .NET :)

[@jrandallsexton]

lol

[@denyspapushaiev5604]

Master of .NET

[@UntoldSecrets1]

I am trying to learn the idea of microservice, is it like that microservice architecture has to be deploy on docker containers? we can use Azure? an old monolithic huge application deployed to IIS, if revamped to microservice architecture we need to upgrade deployment to some cloud based technology also. like docker/kubernates/azure or we have to use AWS? cannot use IIS . right? please accept my apology since its a beginner's question and this video is starting right from the microservice not comparing old architecture (N-tier or SOA) with microservice architecture . PLEASE RESPONSE to my query.

[@UntoldSecrets1]

one more thing to add here. the architecture diagram did not list oracle / mysql / couchbase but we can use any DB in this architecture having it designed based on service by service? i have forked the application a few months before but did not go through it yet.

[@manuelguerrero9917]

Excellent work, thank you.

[@sebainones]

Great talk. It's really helpful

[@AzDev-CommV]

I really like this one! 😎

[@travisarndt853]

Great job

[@jrandallsexton]

Another great job, Cesar.

[@gavinluo5707]

thanks you , hope to give more videos to study eshop architecture

[@saeidbabaei7897]

Greate Cesar. Thank you.

[@DevTram]

I am gonna convince the world that .NET can compete with JavasScript runtime environment that are so trendy these....

[@algorithm-artisan]

Pure Microsoft JABAHHHHH What did i expect, its .NET show

[@mennolaan2468]

didnt the title of this video gave that away, what did you expect? ruby on asp.net core?

[@carlosreis9775]

Thank you

[@Zixtys]

We actually put a Load Balance in front of our API Gateway to create a reverse proxy and cut down on DDOS threat

[@arvn5221]

Sub-titles @9:25 to read as "Xamarin forms" instead of "summer in forms"

[@buildingphase9712]

Microsoft is probably the best company ever. . .Thank you

[@tplummer217]

I wish they had driven deeper into the service call chain issue. The nature of the business problem you’re trying to solve sometimes dictates the number of required interactions among services. Its not just data being managed by each service , they also perform real actions that need to be part of some operation to complete a process.

[@shashikanthmk3360]

Very Informative. Thank you.. :)

[@trxe420]

Great job! very informative

[@shamilJaey]

How do you handle code logic duplication in different microservices ?

[@petersonandradetube]

Great

[@regestea]

why we don't have Microservice for beginner😒😒😒😒

[@stefangabor5985]

Maybe the app is great, however, the speaker is not very convincing, and it seems confused when answering simple questions. I would have picked a better speaker and a better interviewer, maybe Scott H.

[@lipslidemyrail]

The gateway sounds like an anti-pattern. You have to basically make twice as many (expensive) network calls than if you just call the microservice from client application code. I'd rather just deal with the security and management of multiple urls in my client application code.

[@JRLawhorne]

I think the justification for a gateway is that the network call from your mobile app to the micro-service or gateway is generally much more expensive (in latency and bandwidth) than the network calls between the gateway and your services. So, instead of 5 expensive calls from mobile app to micro-service, you make 1 expensive call from mobile app to gateway and gateway makes 5 cheap calls to the micro-services.

[@tkousek1]

Ihmo, I think the gateway is intended to act as a facade which serves up "view models" while abstracting away the domain models for all of the backends that can perhaps "come and go or morph into other backends as the application changes". I feel it's very good for large/complex applications (ie, Amazon, Facebook, etc..). For a very small application where the backend may not change for a long time and only 1 or 2 devs are working on it, it may be a viable approach to not use it. I saw a seminar about "technology envy" which deals with that same issue. It basically says "Just because everyone else is using all of the cool stuff in their apps, it can be a bad thing to do the same in your apps just for the sake of it.". Then they go on to say that Martin Fowler even suggests there are times when it's not worth decomposing a monolith into a microservice. So in your case, it could be an anti-pattern in much smaller applications that can be easily maintained by 1 or 2 devs. In a large scale application(s) at Amazon/Microsoft/Facebook, etc.. the gateway (BFF) can eliminate a lot of headaches while allowing freedom for additional unit testing and container/orchestrator configurations without the client needing to be impacted. Just an opinion of mine and nothing more as others may feel different and I respect that.

[@DJosh-cs5vx]

@@JRLawhorne brilliant analogy and on point.

[@nielsSavantKing]

'We worked six or seven years together'... "in here??" "yes at microsoft". Nothing to do with the quality of the video. That is awesome. But this guy is nervous or has a lot of stress

[@chriscardoz]

Just a pile of spaghetti.... 😂

[@tisurmaster]

when is the video useful? I ain't got all day.