Now let’s look at our next business layer which is PreBus. The PreBus handles all the API requests whether it's an input or the requested output. Prebus can be found in the in the orchestration layer.
Web Controllers receive the request as web api, does the basic attribute validations and passes on the control to the PreBus project which consists of the Services that validates the request for all inputs and passes the control back to the user with success or failure of the execution of the input. It also takes care of receiving the input and gives the result back for the various query operations for the application which are used to view the data.
The PreBus validates the request for all inputs and passes the control back to the user with success or failure of the execution of the input. In case of eventual consistency, the Services makes sure that the data is put into the chosen Bus. Further, if you don't want eventual consistency and don't want to put the data into the bus for processing in an asynchronous manner, PreBus takes care of that. It also provides the option to store data or interact with the database directly without skipping the bus.
We will go into the detail when we learn about the Crud.