Adapters and Infrasctructure

[Erandir Junior]

I have difficulty understanding some things related to clean architecture, such as the connection between the infrastructure layer and that of the adapters, as I see a certain dependency on use between them, correct me if I'm wrong:

Can my controllers depend on a route lib interface for example?

Can my gateways use something directly from orm, or do I need to create an interface for orm as well?

I see that decoupling is something that would take some work, at least in the cases above.

If you have examples of code and projects that implement clean architecture correctly, I would be very grateful to see them.

[Paul Michael Reilly]

Erandir, you might get better results if you post your question to the #clean-code-discsussion channel on the Clean Coders Slack workspace. Here's an invitation.

-pmr

--
The only way to go fast is to go well.
---
You received this message because you are subscribed to the Google Groups "Clean Code Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clean-code-discu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/clean-code-discussion/99c3cb0a-d0fa-47d6-a99a-0789905860d1n%40googlegroups.com.

[Romain LAGARDETTE]

https://github.com/jasontaylordev/CleanArchitecture

--

[Łukasz Duda]

In my implementation of clean architecture I've noticed the following:

• Controller has many meanings. My controller, like in the example https://docs.microsoft.com/en-us/aspnet/mvc/overview/getting-started/introduction/adding-a-controller, translates between ASP.NET MVC Framework and use cases. HTTP request is routed to particular method, which calls use case activator. Use case activator is the facade with it's own interface, that doesn't depend on MVC Framework.
  
• Since use case depends on gateway interface, gateway implementation can use ORM directly. https://www.martinfowler.com/eaaCatalog/gateway.html The gateway implementation "translates the simple method calls into the appropriate specialized API", in this case into ORM API. The the gateway implementation is "interface adapter". It translates between gateway interface and ORM.

Regards

Łukasz

[Erandir Junior]

I could not access

To view this discussion on the web visit https://groups.google.com/d/msgid/clean-code-discussion/CAGwjgEjPCz8mkK5QEgnE77Eq03LGGMv_kE5FzOXP3SQwtg0Nfw%40mail.gmail.com.

--

Atenciosamente,

Antonio Erandir Feitosa Soares Junior

(85) 98112-7588

[Erandir Junior]

But wouldn't that violate the dependency rule?

Because in this case you are using an outer layer feature, directly on an inner layer.

[Łukasz Duda]

I don't think so. That's the role of adapter. Adapter depends on each side and nobody depends on adapter.

Of course if you look at the picture of dependencies https://blog.cleancoder.com/uncle-bob/2012/08/13/the-clean-architecture.html it seems like DB depends on Gateways and Web depends on controllers. Probably the picture is gently misleading in this regard.

[Erandir Junior]

I just made an image showing the flow in both cases, first creating abstractions and the second using external components directly from the adapters layer.
https://drive.google.com/file/d/1-G7GJzisWMGqVG8tHm6WElhvmyrLSPTs/view?usp=sharing

[Erandir Junior]

So, this is my biggest question about this, how far can I faithfully follow the image proposed by uncle Bob, creating abstractions even for external components? Use external components directly in adapters?

And your answer makes a certain sense, yes, I would even like to see an answer from Robert C. Martin, agreeing or refuting your point of view.

Em quinta-feira, 4 de março de 2021 às 11:30:09 UTC-3, lukasz....@gmail.com escreveu: