Tweet
Tweet

Slide 1

Slide 1 text

Deptrac Clean Up Your Architecture SensioLabs

Slide 2

Slide 2 text

SensioLabs Andreas Hucks CTO @ SensioLabs Germany @meandmymonkey

Slide 3

Slide 3 text

SensioLabs

Slide 4

Slide 4 text

No content

Slide 5

Slide 5 text

SensioLabs The Problem • Getting legacy code under control • Gain insight into applications • Constrain changes to boundaries defined by your architecture

Slide 6

Slide 6 text

SensioLabs Clean Packages • Separate your business code from your framework • … or in fact, any other 3rd party libs • Separate your own layers (Domain, Application, Infrastructure…)

Slide 7

Slide 7 text

SensioLabs github.com/sensiolabs-de/deptrac Deptrac

Slide 8

Slide 8 text

SensioLabs depfile.yml

Slide 9

Slide 9 text

SensioLabs Demo Time

Slide 10

Slide 10 text

SensioLabs Drill down • Create multiple depfiles to create different views on your code • Enforce rules on different levels - inside your domain, or between top level packages

Slide 11

Slide 11 text

SensioLabs What can you do? • Use it. Test it! • Other output formats • More Collectors • Exclusions to allow specific deps

Slide 12

Slide 12 text

SensioLabs Tim Glabisch @timglabisch and all contributors github.com/sensiolabs-de/ deptrac/graphs/contributors Kudos

Slide 13

Slide 13 text

Thanks! joind.in/talk/5f724 SensioLabs