In this series, we're going to walk through the database design of our Workflow app and show each part of the solution was implemented, and finally how they were all wired together 

How you shouldn’t implement base classes

public class Entity<T>
{

  public T Id { get; protected set; }

}

Motivation for such code it pretty clear: you have a base class that can be reused across multiple projects. For instance, if there is a web application with GUID Id columns in the database and a desktop app with integer Ids, it might seem a good idea to have the same class for both of them. In fact, this approach introduces accidental complexity because of premature generalization. 

There is no need in using a single base entity class for more than one project or bounded context. Each domain has its unique path, so let it grow independently. Just copy and paste the base entity class to a new project and specify the exact type that will be used for the Id property. 

SOLID Design Patterns 

As a web designer, it’s hard to stay organized. Not only are you balancing several projects at once, but you’re likely facing tight deadlines and tough clients as well. You may also be bouncing from brand to brand, and having to constantly learn new brand guidelines and styles. 

A curated list of Domain-Driven Design (DDD), Command Query Responsibility Segregation (CQRS), Event Sourcing, and Event Storming resources 

This type of effect is notably used in portfolio-type situations where the design intends to show both visual and informational details. 

9 best site builders for designers