This document discusses Onion Architecture, its origins and benefits. It describes Onion Architecture as allowing the deferral of critical design decisions. The core focuses on domain objects and business rules while external layers deal with interfaces, frameworks, databases etc. This allows for independence of components, high cohesion, low coupling, and improved testability and maintainability. Examples of implementing Onion Architecture in code are provided as well as references for further information.

1. Desvendando o
Onion Architecture
Guilherme Lacerda
Wildtech - UniRitter
@guilhermeslac
Maurício Andreazza
Canoastec - UniRitter
@oandreazza

2. Guilherme Lacerda Maurício Andreazza
Quem somos?

3. Onion
Architecture?
Lean
Architecture?
Clean
Architecture?
Ports and
Adapters?
Hexagonal
Architecture?

4. Uncle Bob
Origens
Alistair
Cockburn
Jeffrey
Palermo
Nat Pryce e
Steve Freeman

5. “A good architecture allows
you to defer critical
decisions like the UI,
frameworks, database, etc.”

6. MVC

8. Anatomia

9. Anatomia

10. Onion

11. Inversão de
Dependência
DDD
Testabilidade
Manutenibilidade
Independência
de UI, BD...
Benefícios
Alta Coesão,
Baixo Acoplamento USar as ferramentas
como... ferramentas
SOLID na cabeça!

12. Smells
Overengineering
Implementação
errada dos
conceitos
Quebrar o Rule
Dependency

13. Exemplo 1
https://github.com/oandreazza/onion-architecture-tdc

15. Exemplo 2
https://github.com/guilhermeslacerda/CleanArchitectureExample

17. Links
http://alistair.cockburn.us/Hexagonal+architecture
https://8thlight.com/blog/uncle-bob/2012/08/13/the-clean-architecture.html
http://jeffreypalermo.com/blog/the-onion-architecture-part-1/
http://martinfowler.com/eaaCatalog/separatedInterface.html

18. Principais Referências

19. Questões??

21. Obrigado!!
Guilherme Lacerda
Wildtech - UniRitter
@guilhermeslac
www.codingbyexample.org
Maurício Andreazza
Canoastec - UniRitter
@oandreazza
blog.oandreazza.com