Just came to say that your OpenTelemetry course is actually sick. Just finished it. Good job!

Thank you for the video. I'm studying it to implement it in my work. It'll be the best way to solve our problem.

Thank you for sharing your thoughts. I find them exciting. My thoughts went to Whitehat Hackers. One could argue they operate under a shared codex /code of conduct. Thank you for making great content. 🎉

Do we need a well defined code of conduct specific for this industry? Being a decent person, doing the right thing, not using your technical skills to cause harm and damage to others should be enough. There are lots of professions, general code of conduct applies to all. I feel that All the points you mentioned applies and are being practiced, and it actually forces us to comply, otherwise we can lose our job and we lose credibility...

Hello. How come not having a repo here doesnt break encapsulation? How come having "too many" get methods breaks SRP? We are just working with database and then entire DbContext is a big SRP breaker. Interfaces also a thing. There are things called Read/Write models and CQRS for a reason. Repos for writes belong to domain layer, cause those "too many" get methods should come from a business. TLDR: you unit test repo if it has any mapping logic, you can integration test it independently if you want.

Key points At the time when commertial open source was driven by Java developers and unit testing was a cool new wave, Microsot thought that unit testing can be sold for professionals. So MSTest was available for VS Professional subscribers, but not for Cmmunity Edition version. A funny fact: MSTest still has [Author] attribute. The person to blaim when test fails.

Uncle Bob in one of his presentation said that "We are an unregulated industry, but it's only a matter of time or luck, that a HUGE incident will happen, with human casualties and then politicians will come and regulate us". I believe that this is very close to what you mention in your video. We need to protect our industry by getting self-regulated (really close to a Code of Conduct, as you mention). If someone else does this for us, it won't be fun...

Yay! See you in Porto!

I would it if you could make a video that shows how to return an interface that is a value type from a struct that implements that interface. It’s possible, but I only know one way of doing it; perhaps you know a better way.

Ouch! That last bit can bite you. Man,that’s not right. They need to fix that.

I’ve used this long before it was ever given a name, and while most know it as Hex Arch, I call it XPlicit Arch, since architect is supposed to be about interfaces and contracts, not implementations. For you C guys out there, when he speaks of Ports, think Interface or abstract class, and adapters can be 2 things (either an interface implementing class or abstract class that implements that interface but serves as a translator). There is some cost to this architecture, as it’s not easy for junior or mid level coders to fathom at first, but it pays off for enterprise solutions. It’s Dependency Injection intensive, so it makes people code to interfaces, another plus. Also, it doesn’t have to be followed exactly, and you can use it as your enterprise core architecture, which it is ideal for, but it can also be applied in an complex application as well. For instance, a web portal might have it’s own entire hexagon that interacts with the “Core” enterprise hexagon. The main thing to realize is that nothing deals with concrete instances except the deepest regions in the Core of each hexagon. Everything is talking to each other via interfaces, allowing for future change and flexibility. Search “The Software Architecture Chronicles” by Herbert Graca for a thorough explanation on this architecture.

Thanks for the clarification. But why do people not include oData in this kind of comparison? Is it only used with .NET?

I am using REST, gRPC and GraphQL in my projects. - gRPC for synchronous communication between microservices. or for client-server communication when a server can call methods from client - GraphQL HotChocolate for frontend-backene communication. I can't imagine my life without GraphQL, it's so much easier with it. And much more productive. You can combine multiple queries on the frontend and get what you need efficiently. When you need to show table view data on the frontend with filtering, sorting and paging support - HotChocolate has these all built-in that automatically integrates with EF Core. - for the frontend we also use code generation to generate all the types from the GraphQL schema, it significantly makes us more productive.

Once I used Graphql with strawberry library to consume an array of large objects and the performance was horrible, multiple times slower than rest. With my small knowledge/experience with Graphql, I imagine it is better than rest only for BFF and small requests as you said.

but rider isnt free...

Great video that explained it very well. But I feel like everything can be simply created using Mocking libraries For example, a mock might be heavier than dummy, but serves the purpose Mock might be heavier than stub, but we can still configure it to return the expected result. If you think that there is complexity in setting up and doing duplication, we can do the following Assume, we use xUnit. In that all mocks should be private fields. And we introduce private methods where we setup all mocks as expected. For example, we want to run a test where a stub should return false. Simply add a private method that says SetupServiceAToReturnFalse(), and continue the test. We can add similar to true as well In arrange section, call all setup methods for the mocks and continue the test. Also, we can configure every mock with general values in constructor which can be overridden in mock's setup private methods. So, we make test method even simple by only overriding the default mocks I appreciate so much details added in this video. It is necessary to understand all the concepts to know how we can do without library. But mocking libraries such as Moq really simplified it all. Please let me know if something may go wrong with the above setup on any scenario

Hi, may I know what IDE you are using in your video? Thanks.

Awesome. Thanks for the video

ّ

These properties seem to be missing from the new API. How do you configure them? logging.IncludeScopes = true; logging.IncludeFormattedMessage = true;

Thx again for your video. I have difficulty understanding. Because if I have a GenreService class with a lot of business logic that calls this repository. If I remove GenreRepository, I will then have to inject the DbContext directly into my service class. As a result, regarding unit tests, I will no longer be able to use a fake repository? Furthermore, can we have repositories in some cases and not in others? How does that affect the coherence of the project?

What if _store.UpdateAsync(...) throws an Exception ? You still need to surround the code in your UpdateAsync method with try/catch block. Exceptions have a cost, OK, but by definition they don't happen often.

Hi Gui! Great video explaining the historial why of the repositories, the sense of having them and/or testing them, and showing an alternative... And yes please, do a video explaining the Specification pattern! Thanks again

Great viseo. Would be nice to have a video about specification pattern, thanks!

Please don't unit test repositories. Write integration tests for your use cases with a real database. It will cover your data access testing, whether you use repositories or not. Be pragmatic.

Interesting topic , by the way last week i watched your (NDC) stand talk and its amaaaaaaaazing 👌

Yes please to specification pattern 🎉👍👌

The two question that remain in my head: 1. When using domain centric architecture, shouldn't you use interfaces declared in your domain to be implemented by infrastructure logic? How does that work with efcore DBContext? 2. Microsoft explicitly says to not use the in memory provider due to compatibility limitations, what's your reason for promoting it and would you agree using sqlite in memory would still be a unit test?

Before people start spamming that these EF-wrapper-repositories are useless. There is real use case for these repositories when you want to restrict access to only specific entities (aggregate roots most likely). EF just gives you way too much freedom when using it for mutations. It's so easy to accidentally skip domain logic when you can just query any entity from any point of tree or fetch the root only partially. I usually use EF only for mutations and query with something else, like Dapper for example (cqrs style).

This nonsense started with Java and followed by DDD books for enterprise corp coders, its dead. use a Dao NH Session(), EF Context() are by nature a Repository, the years of people writing classes on top of classes..

Please do the video about specification pattern, also your view about unit tests was pretty constructive.

So the industry gave up on checked exceptions and then realized that code can fail without the caller knowing about the potential failure points. Now we're coming up with an entire new concept (that BTW loses the stack trace information), all to avoid just using checked exceptions that the language supports by design?

¿Why do you recommend using a library? Because that is the approach i want to take but it´s hard to pitch it to the team.

I believe it is because the navigator did an excellent job of directing (using) chatGPT. Meaning, it is also in the user how well they know their craft. But that is indeed amazing demo of the crazy capabilities of the GPT.

Thanks for your video. I like these design pattern videos.

Good explanation thanks. How can I identify the real problem for ex. an exception is throwed and I want to log it? Aren't we ignore valueable exception data by using Result pattern?

Rust influencing C# as well? 👍

Great video. I fear looking at the code of the people saying "but why".

it feels unnatural in C# community, but this is all until Microsoft would finally implement descriminated unions feature. Nick Chapsas just had great video reviewing proposal feature even with some code examples and details. Not sure I am happy that part of the feature works using reflection in runtime, but this is still pretty solid step.

+1 for result pattern

Great tutorial thanks!

i Always use Result<T,E> and my implementation have methods like Rust(map, bind,unwrap and so on). I love It, but i can t use It with my team 😢

Thanks a lot for your video. I agree that readability is the main advantage of the result pattern or monad. Exception can be see as a Go To. A good video on this topic is "Throw Exceptions Out of Your Codebase" by Guillaume Faas. However, performance should not be the deciding factor. I conducted a benchmark and found that the difference is not significant.

6:47 no rickroll? :(

I like how you talk about the pros and the cons, this honestly seems situational but not really scalable

This video is proof that my studies and thoughts are on the right track. I managed to have the same idea, the same conclusion as an MVP star.

Great content! Thanks like always!

Result Pattern, Result Pattern, but remember it is not a solution for all issues. If you have complex logic, multiple level of call hierarchy, and any issue in the code will break the whole execution, there is no need to use Result Pattern and mess your code with thousands of if(result.Success) but it is much better just to throw an exception, catch and handle in global exception, and keep your code clean and readable

This - I have my own implementation (unfortunately) in company code base but it fulfills the goals of don’t throw if you can return error The only unsolved problem due to time constraints is what if want to have different behavior based on error code (rn it is ugly if statement in a few places) To be satisfied with result type in .NET you need to add a little bit of ext method on Task type also you can chain them if you want to

please dont