Principles of PHP Package Design - Dutch PHP Conference 2014
Upcoming SlideShare
Loading in...5
×
 

Principles of PHP Package Design - Dutch PHP Conference 2014

on

  • 400 views

Slides for my talk "Principles of PHP Package Design" at the Dutch PHP Conference 2014 (http://phpconference.nl).

Slides for my talk "Principles of PHP Package Design" at the Dutch PHP Conference 2014 (http://phpconference.nl).

Statistics

Views

Total Views
400
Views on SlideShare
394
Embed Views
6

Actions

Likes
1
Downloads
11
Comments
0

2 Embeds 6

https://twitter.com 4
http://librosweb.es 2

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Principles of PHP Package Design - Dutch PHP Conference 2014 Principles of PHP Package Design - Dutch PHP Conference 2014 Presentation Transcript

    • Principles of PHP Package Design Objectoriented design for packages Matthias Noback - PHP developer and consultant Dutch PHP Conference - 6/28/2014
    • Matthias Noback Noback's Office PHP developer Consultant, writer Proud father · · · 2/50
    • Blog php-and-symfony.matthiasnoback.nl 3/50
    • A Year With Symfony leanpub.com/a-year-with-symfony 4/50
    • Tight coupling Coupling to a framework 5/50
    • Code 6/50
    • Squiggly lines 7/50
    • Code 8/50
    • Packages There are many different kinds 9/50
    • Class design 10/50
    • Package design Nothing? butunclebob.com 11/50
    • Principles of PHP Package Design leanpub.com/principles-of-php-package-design 12/50
    • Package design Cohesion 13/50
    • Package design Coupling 14/50
    • A - Cohesion principles Perspective: the package in isolation 15/50
    • 1 - The Release Reuse Equivalence Principle The granule of reuse is the granule of release 16/50
    • 1 - The Release Reuse Equivalence Principle Version control and hosting Composer package definition Meta-files Auto-loading · · · · Semantic versioning Quality control · Branches Tags Backward compatibility - - - · 17/50
    • 1 - The Release Reuse Equivalence Principle If you don't have the time to turn your reusable code into a proper package... Don't release it. 18/50
    • 2- The Common Reuse Principle Classes that are used together are packaged together If you use one class of a package, you will use all its other classes too. 19/50
    • 2- The Common Reuse Principle Smell: Feature strata 20/50
    • 2- The Common Reuse Principle Example of feature strata: the Symfony Security Component 21/50
    • 2- The Common Reuse Principle Smell: Classes with different dependencies 22/50
    • 2- The Common Reuse Principle Example of different dependencies: Gaufrette 23/50
    • 2- The Common Reuse Principle Different dependencies: Gaufrette { "name":"knplabs/gaufrette", ... "suggest":{ "knplabs/knp-gaufrette-bundle":"tousewithSymfony2", "dropbox-php/dropbox-php":"tousetheDropboxadapter", "rackspace/php-opencloud":"touseOpencloudadapter", "herzult/php-ssh":"touseSFtpadapter", "phpseclib/phpseclib":"tousePhpseclibSftpadapter", "aws/aws-sdk-php":"tousetheAmazonS3adapter", "amazonwebservices/aws-sdk-for-php":"tousethelegacyAmazonS3adapters", "doctrine/dbal":"tousetheDoctrineDBALadapter", "microsoft/windowsazure":"touseMicrosoftAzureBlobStorageadapter", "ext-zip":"tousetheZipadapter", "ext-apc":"tousetheAPCadapter", ... }, ... } 24/50
    • 2 - The Common Reuse Principle Leszek Prabucki's response 25/50
    • 3 - The Common Closure Principle Classes that change together are packaged together 26/50
    • 3 - The Common Closure Principle Reasons for change The application's features change The business rules change The web framework's best practices change The persistence library's configuration changes ... · · · · · 27/50
    • 3 - The Common Closure Principle Smell: code for multiple application layers Web User Interface Command-line interface Model Infrastructure services · · · · 28/50
    • B - Coupling principles Perspective: the package in relation to other packages 29/50
    • 4 - The Acyclic Dependencies Principle The dependency graph of packages must have no cycles 30/50
    • 4 - The Acyclic Dependencies Principle 31/50
    • Stability Something is stable if it's resistant to change. 32/50
    • 5 - The Stable Dependencies Principle An irresponsible package 33/50
    • 5 - The Stable Dependencies Principle A dependent package 34/50
    • 5 - The Stable Dependencies Principle An instable package: irresponsible and dependent 35/50
    • 5 - The Stable Dependencies Principle A responsible package 36/50
    • 5 - The Stable Dependencies Principle An independent package 37/50
    • 5 - The Stable Dependencies Principle A stable package: responsible and independent 38/50
    • 5 - The Stable Dependencies Principle Depend in the direction of stability 39/50
    • 5 - The Stable Dependencies Principle Counter example 40/50
    • 6 - The Stable Abstractions Principle What is more likely to change? Something concrete or something abstract? A class or an interface? · · 41/50
    • 6 - The Stable Abstractions Principle Abstractness should increase with stability 42/50
    • Summary Reuse/release equivalence principle Common reuse principle Common closure principle Acyclic dependencies principle Stable dependencies principle Stable abstractions principle · Reuse only code that you can release as a product.- · All code in a package is reused at the same time.- · Code in a package only changes for a few reasons.- · No cycles in the dependency graph.- · Only depend on more stable packages.- · More stable packages are also more abstract.- 43/50
    • Word of advice You can't maximize them all at the same time. Keep them in mind while you are working on a package. 44/50
    • Principles of PHP Package Design leanpub.com/principles-of-php-package-design I'm impressed. — Robert C. Martin 45/50
    • Principles of PHP Package Design Get a 10 dollar discount: http://leanpub.com/principles-of-php-package-design/c/dpc2014 46/50
    • Questions? feedback joind.in/10883 twitter @matthiasnoback leanpub leanpub.com/principles-of-php-package-design 47/50
    • Image courtesy Clean Coders GitHub BitBucket Packagist PoEAA But Uncle Bob Robert Martin · · · · · · · 48/50
    • 50/50