Interested in a private company training? Request it here.
Getting the software right is a hard thing to do. This is because business and developers do not always talk the same language. Domain Driven Design is all about getting the language right between them.
So what is a modern web application? One that uses Angular and TypeScript? With the speed that modern web application developement evolves, there is the chance that your web site uses 'old' technology by the time it is done. But sound architecture never goes stale. As a wise man once said: 'If you think good architecture is expensive, try bad architecure'.
Every developer want clean code that works. So how does one get to maintainable and working code? And moreover: keep it working.
When Unit Testing, you will have to decide on frameworks. There are several ones out there, which one do I need? Visual Studio comes with a built in framework called MSTest, but you also have others, like the popular XUnit. In this module, we will discuss pros and cons of these frameworks, and go into some best practices. How do I know if I have tested enough? With code coverage you can see which paths in your code you have tested, and easily discover untested conditional logic.
When constructing the domain model, there are several approaches. Tactical Design provides a set of technical resources that are used in the construction of the domain model. The goal is to enrich your domain model by applying these standards correctly. When done so, it will reflect your business model with more clarity.
DDD distinguishes between entities and value objects. How do you implement these?
Some behavior cannot be easily mapped to an existing entity or value object. In this case we put this behavior into a domain service. And how do we group our entities and such? Into modules.
One of the core pillars of DDD is Strategic Modeling. Strategic modelling helps you at defining the Bounded Contexts, the Ubiquitous Language and Context Maps.
Grouping your entities in Aggregates can make development easier, and help to avoid the "Death by a Thousand Dots" anti-pattern. Entities have a life cycle, and how do your create complex hierarchies of entities?
When a database is designed, the idea is to normalize data, i.e. avoid duplicate data. When designing the object model for an application you try to come up with a design which is best suited for solving your business problems. This means that mapping tables to classes one-on-one is often a bad idea. Entity Framework allows us to map the relational world to the world of objects, allowing more complex mapping.
With .NET 5 also comes a while new Entity Framework Core. A new implementation of EF, which can run cross-platform, on Windows, Mac and Linux.
Mapping in EF Core uses conventions, attributes, or Fluent API. You will see how to use these to model your database in EF Core and apply the changes with Code-first Migrations.
Domain Driven Design is a great way to start designing your applications. Entity Framework Core is a great framework to access and manipulate your data, stored in databases. Now, how can we fit Domain Driven Design concepts into Entity Framework Core? Yes we can!
When building larger applications you want to keep low coupling and high cohesion. So how do you implement changes that need to be handled by different sub-systems?
When creating modern web applications with ASP.NET Core MVC, it's not that straightforward to unit test the Controllers and Views. How does one validate wether the ActionResult returned by the Controller action is the one you wanted, as well as whether the View is correct. How do we replace dependencies during testing with MVC? How do we perform end-to-end testing?
When architecting and developing applications, there are several approaches that could be considered. Domain-Driven Design (DDD) is one of them. The idea of domain-driven design is to let the software originate from the so-called domain. By doing so, one tries to create software that perfectly mimics the domain it was created for. When creating business applications, there is often a need for a data access layer to some database. This is where Entity Framework Core (EF) jumps in. In fact, domain-driven design and EF Core can go perfectly hand in hand. This course will discuss the concepts of domain-driven design and how EF Core can help you at implementing these concepts. Building a large website can turn into a very complex project if you are not careful, so we will split our solution into layers. Best practices today is using an architecture approach called "Clean Architecture", which separates your solution into different layers with maintenance and testing in mind. DDD works very well for long-lasting software projects that will undergo many changes triggered by changing and new requirements. How do you ensure that existing functionality doesn't get broken? This is where testing comes into play. Participants learn about modern architecture and will get a hands-on approach to building a web site using C#, DDD, EF Core and Unit testing.
Attendees are required to have prior knowledge of C#/VB.NET and ASP.NET MVC. This course is given in C#.