# Closing thoughts on A-Frame architecture

Phew, that was a lot. I'm always surprised how simple solutions contain so much detail and nuance when I try to explain them. I hope I conveyed the message that A-Frame simplifies code within a module or class by separating the infrastructure components and logic components. They will interact with each other through a controller that knows how to connect one to the other. Keep logic focused on the feature and try to keep infrastructure as straightforward as possible.

Good luck out there!

## Sources

[A-Frame Architecture with Wolverine](https://jeremydmiller.com/2023/07/19/a-frame-architecture-with-wolverine/)

[James Shore A-Frame Architecture](https://www.jamesshore.com/v2/projects/nullables/testing-without-mocks#a-frame-arch)

[Wolverine Docs](https://wolverine.netlify.app/tutorials/)

[Integration testing in dotnet](https://learn.microsoft.com/en-us/aspnet/core/test/integration-tests)

[TUnit](https://tunit.dev)