Stop using HTTP from IHandleRequests implementations

[mauroservienti]

Currently IHandleRequests implementations use HTTP to talk to their back-end services. That's not needed, and lead to confusion. It leads people to believe they must use HTTP, but in reality since they logically belong to a service they can easily access service data directly.

[markphillips100]

So @mauroservienti, to take the sales service as an example, does this mean the Sales.Api project is redundant? In other words, the Sales.ViewModelComposition project can instead go direct to the database from (HTTP GET) handlers?

[mauroservienti]

In essence yes. I'm not sure I'll remove the API projects because it'll require too much effort to explain why handlers can go directly to their own databases. I'll probably add a comment in the handlers stating that going through HTTP is not required.

[markphillips100]

Good to know nonetheless. Thanks for the input Mauro.

On Tue, Apr 7, 2020 at 12:43 AM Mauro Servienti [email protected] wrote:

In essence yes. I'm not sure I'll remove the API projects because it'll require too much effort to explain why handlers can go directly to their own databases. I'll probably add a comment in the handlers stating that going through HTTP is not required.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/mauroservienti/all-our-aggregates-are-wrong-demos/issues/105#issuecomment-609837950, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABPTGNKNDPOR3DDT6BGCYBTRLHTCLANCNFSM4JMCVGXA .