Components overview

The data processing and retrieval logic in the solution generated using Entity Services is organized into components connected in ‘pipelines’.

Similarly to the CQRS architectural pattern, the code implements two separate pipelines: one for reading and serving the data and one for updating and storing it.

Each pipeline (or, to be more precise, each pipeline component) implements the same set of methods. For example, the Write Pipeline implements the Create, Update and Delete methods, and the Read Pipeline implements the usual data retrieval methods like GetById, GetAll, etc.

If required, you can add additional methods and implement them in all the components.

It is important to mention two ways to extend the components - either for all the entities in the entity group (using generic classes in the Extensions project) or for a specific entity type.

Here are some of the components you can use in your read or write pipelines:

• Read Pipeline Components:

  • Custom,
  • MongoDb,
  • Entity Framework

• Write Pipeline Components

  • Validator,
  • Custom,
  • MongoDb,
  • Entity Framework

The storage components should be of the same type. You can’t mix them and have, for example, NoSql read component and Sql write component.