วีดีโอ

ممنون باباجان❤️

Glad it was helpful, enjoy holidays:)

I'll go for the first approach, the important thing here having a single connection to cosmosdb, it is exactly like calling a third-party API, you'll create a HttpClient with a base address (here is the connecitonString) and call different endpoints (here is the containername).

@sa-es-ir Thank you for the details.. But I have one query, I have created a project with 1st approach 1., In a single AppDbcontext Onmodelcreating calling only once 2. When I send a request for another tenant Onmodelcreating is not getting called.. 3.Using AddDbContextFactory in Di container Please let me know to resolve this

@@ArjunRR-cz8hb Do you have a code like mine in this video? if yes then please provide a github repo then I can see the code and talking about the actual problem.

Glad you like.

Glad it was helpful!

Glad it was helpful!

Yes, correct. Basically we need to do two steps: 1- cleanup migrations and database (this video) 2- remove the properties that already cleaned up in previois step from the code

I'm pretty good, thanks:) Glad you like the video

ممنون از اینکه با دقت ویدیو رو تماشا میکنی! هر کشوری لهجه خودشو داره اگر تو محیط انیترنشنال کار کرده باشی به راحتی متوجه لهجه انگلیسی حرف زدن هندی ها، فرانسوی ها(وحشتناک)، روسی ها و.... کاملا طبیعی هست!

@@sa-es-ir منظورم لهجه نیست ،تلفظه.

They mentioned in the ticket that it will take years to fix!!

While using Channels is ok for doing the same purpose, I find it more complicated to work with. Basically, I always like the visibility in the code, no magic behind the scene happening.

Thanks! I'm glad you liked it.

Glad you like the video and awesome suggestion about using yield, I didn't think about this option, thank you for the input.

محسن این سامانه استعلام یکپارچه دیگه بخشی از خاطرات ماندگار منو تو شده:)))

Glad you enjoyed:)

Happy you like the video

You are very welcome

Well in the video I created a decorator on top of the `Generated` grpc service in the SDK, so basically API depends on the SDK (the decorator service), what we want is not depend on any generated grpc classes from the caller side (the API). If there are some changes on the GRPC server and there is some direct dependencies to it then all those clients will be failed but if inside the sdk decorator we handle all the exceptions then we are safe from breaking those callers, at least until we change the SDK!

@@sa-es-ir sounds good. I got your point. :) thank you

The best way is using a message queue, so one instance will send a message and the other side there is a consumer listening on same queue to process and sync the state.

Thank you:)

Very happy it was helpful to you, please support me by sharing my videos to your network, would be appreciated 🙏

@@sa-es-ir I already shared to my network. 👍

@@mahdiyar6725 Thanks for the great sum up and totally agree.

@@SamH-h1v Thanks and happy you like it

Thank you and happy it was helpful. About the error, please follow the code in my repo the link is in the description, better to use localhost:9092 and make sure both Kafka and zookeeper are using same network.

@@sa-es-ir But that's what I'm doing. Is it possible that my error comes from not using docker?

@@cvetomiranedelcheva9946 Are you run kafka and zookeeper both? they have access to call each other? I think better to run in docker to make sure the problem is not in your code

@@sa-es-ir Okay, thank you very much!!

Glad you like the video, you can use Task.Yield as many as you can, no issue with that but better to use it when needed to avoid extra overhead for runtime. I didn't get the second question, can you explain more.

Glad it was helpful!

Happy you like it

Glad you like it 🙏

I didn't use it in a production project, I'll check it.

Good question, the Consumer needs to tell kafka to commit the message, either auto-commit by kafka lib or manually commit by developer, the point is you need to handle the validation on consumer so if there is a invalid message you just skip that message and commit it without processing.

Nice point and thanks for that, I'll check it later.

Glad you like it, thanks

Thank you

Much appreciate the support, please help me by sharing my video with your friends.

I appreciate Jan, please help me by sharing my video with your friends.

Glad you enjoy it.

Thank you

Thanks for the suggestion, I'll put it in the list

You got the main idea about having required columns only, if you have time to create a simple repo about what you need then we can fix it together, I'd would say it is easy to tell EF core to generate what we want.

@@sa-es-ir Thanks for the reply. I was able to work out the syntax to get what I want in the long run. However, I am now realizing that if you try to include more than one child MANY relationship, performance tanks noticeably. I am aware of the Split() function, but I've come to the conclusion it's just better for me to run multiple queries rather than one or two big complex queries.

I generated the token from auth0.com for my user, basically, I didn't want to cover token generation in this video and I've tried to show how to `validate` that token, no matter where it comes from.

Yes, it can be improving by dequeueing waiting each task via WaitAny mutiple times, but it can increase memory and CPU allocation.

In the worst case, it just behaves like Task.WhenAll()!

@@sa-es-ir U didnt get what he want to say, it is not about worst case, it is about reordering await affects execution time in you approach, if last task will wait 1 sec before exeption, you still will wait 3 sec because of first task 3 sec delay

@@igormelnikov5166 Yes your scenario is perfectly fine and can happen because there is no way to know task priorities, my point is, even in worst case (taking 3 sec) is the same Task.WhenAll which always takes 3 sec. Am I correct?

@@sa-es-ir There is a way to respect task priorities, read my first comment. Worst cases are same in all soulutions ofcourse. But in average solutions have different time

Glad you like it, I would appreciate it if you share this video on your network🙏

Glad you like it, I would appreciate it if you share this video on your network🙏

Glad you like it, I would appreciate it if you share this video on your network🙏

Noted with thanks, stay tunned.

Thank you baba♥

Thank you