New course: Domain-Driven Design: Working with Legacy Projects

My new training course Domain-Driven Design: Working with Legacy Projects went live.

Domain-Driven Design: Working with Legacy Projects

I’m continuing the topic of Domain-Driven Design on Pluralsight. This one is about working with legacy projects.

From this course, you will learn how to be productive with a legacy code base even if it’s a complete mess. Some of the specifics of the course:

  • Implementing the Anticorruption Layer pattern.

  • Creating a clean and maintainable domain model in the environment with an existing legacy code base.

  • Evolving the domain model using Synchronizing Anticorruption Layer.

  • Guidelines to consider before conducting a refactoring or a full rewrite.

As usual, this course contains an in-depth, step-by-step demonstration of how to do all this, as well as the theory behind it which explains why behind the how.

Watch the course here: Domain-Driven Design: Working with Legacy Projects.

You can find the source code for the project on GitHub.

If you need a trial code which grants 30 days unlimited access to Pluralsight, shoot me an email and I’ll send you one.

Subscribe

I don't post everything on my blog. Don't miss smaller tips and updates. Sign up to my mailing list below.

Comments

comments powered by Disqus
Vladimir Khorikov
Vladimir Khorikov
Twitter Email LinkedIn
My book
Unit testing book
Click here to get a 40% discount
Pluralsight courses
Pluralsight ‒ Pragmatic Unit Testing
‒ Domain-Driven Design in Practice
‒ Applying Functional Principles in C#
‒ Database Delivery Best Practices
‒ Specification Pattern in C#
‒ Refactoring from Anemic Domain Model
‒ Domain-Driven Design: Working with Legacy Projects
‒ CQRS in Practice
‒ DDD and EF Core: Preserving Encapsulation
‒ Validation and DDD
‒ Encapsulating EF Core Usage
‒ Prepare for coding interviews with CodeStandard
Most Popular Articles
‒ EF Core 2.1 vs NHibernate 5.1: DDD perspective
‒ C# and F# approaches to illegal states
‒ Optimistic locking and automatic retry
‒ Entity vs Value Object: the ultimate list of differences
‒ DTO vs Value Object vs POCO
‒ 3 misuses of ?. operator in C# 6
‒ Specification pattern: C# implementation
‒ Database versioning best practices
‒ Unit testing private methods
‒ Functional C#: Handling failures, input errors
‒ REST API response codes: 400 vs 500
MSMVP
Recent Articles
‒ Storing information in its highest form
‒ Which collection interface to use?
‒ Generic types are for arguments, specific types are for return values
‒ Modeling Relationships in a DDD Way
‒ Encapsulating EF Core Usage: New Pluralsight course
‒ Collections and Primitive Obsession
‒ How to Assert Database State?
‒ Should you Abstract the Database?
‒ Database and Always-Valid Domain Model
‒ Specification Pattern vs Always-Valid Domain Model
» All articles