Why Architecture in Web Development matters

Why Architecture Lars matters Jankowfsky, swoodoo.com

Lars Jankowfsky • CTO and (Co-)Founder swoodoo AG • (Co-)Founder OXID eSales AG • XP, agile development fanatic • developing since 15+ years • php since php/ﬁ • Software Architect > 10 years Lars Jankowfsky,

Architectur e

Zend Framework symfony cakePHP ezComponent s

(c) istockphoto success (c) aboutpixel.de

Scale!

Speed!

Deploy!

long project lifetime

(c) istockphoto code aging

(c) istockphoto big ball of mud

(c) istockphoto continuous maintenance

„For us, it’s really about scaling horizontally - to that end, Rails and Ruby haven’t been stumbling blocks, compared to any other language or framework. The performance boosts associated with a “faster” language would give us a 10-20% improvement, but thanks to architectural changes that Ruby and Rails happily accommodated, Twitter is 10000% faster than it was in January.“ Blaine Cook, Twitter's lead architect Lars Jankowfsky,

Principles of success

D.R.Y. Do Not Repeat Yourself

Single responsibility quot;if it generates XML then it should not gene principle

K.I.S.S. don‘t think too complex

(c) spackletoe http://www.ﬂickr.com/photos/spackletoe/90811910/) (c) aboutpixel.de

(c) istockphoto (c) aboutpixel.de

Developing

(c) dasbeibi @ aboutpixel.de

Evolving Architecture

Y.A.G.N.I. You Ain‘t Gonna Need it

No refactoring , no evolution.

(c) istockphoto

Principle of „bad smell“

Bad smells? Lars Jankowfsky,

Bad smells? • Do maintenance cost keep increasing? Lars Jankowfsky,

Bad smells? • Do maintenance cost keep increasing? • Simple features need too long to be implemented Lars Jankowfsky,

Bad smells? • Do maintenance cost keep increasing? • Simple features need too long to be implemented • Small changes ripple through your system Lars Jankowfsky,

dead code

dead code data classes

comments „what not why“ dead code data classes

comments „what not why“ long methods dead code data classes

• http://martinfowler.com/bliki/CodeSmell.html • http://www.codinghorror.com/blog/archives/ 000589.html Lars Jankowfsky,

Architecture?

Layered Architecture Lars Jankowfsky,

Layered Architecture • separation of concerns Lars Jankowfsky,

Layered Architecture • separation of concerns • If they can live without each other - why to couple them? Lars Jankowfsky,

Layered Architecture • separation of concerns • If they can live without each other - why to couple them? • Find the boundaries and cut mercilessly. Lars Jankowfsky,

Layered Architecture • separation of concerns • If they can live without each other - why to couple them? • Find the boundaries and cut mercilessly. • Do not bypass any layer! Lars Jankowfsky,

Layered Architecture • separation of concerns • If they can live without each other - why to couple them? • Find the boundaries and cut mercilessly. • Do not bypass any layer! • Separate modules/classes or go SOA Lars Jankowfsky,

SOA Lars Jankowfsky,

SOA • Pro: makes scaling very easy Lars Jankowfsky,

SOA • Pro: makes scaling very easy • Pro: clear deﬁned boundaries, no violations possible Lars Jankowfsky,

SOA • Pro: makes scaling very easy • Pro: clear deﬁned boundaries, no violations possible • Pro: perfect for refactoring Lars Jankowfsky,

SOA • Pro: makes scaling very easy • Pro: clear deﬁned boundaries, no violations possible • Pro: perfect for refactoring • Pro: Deployment beneﬁts Lars Jankowfsky,

SOA • Pro: makes scaling very easy • Pro: clear deﬁned boundaries, no violations possible • Pro: perfect for refactoring • Pro: Deployment beneﬁts • Con: integration testing gets more difficult Lars Jankowfsky,

(c) istockphoto Extend!

(c) istockphoto Scale!

Database

ZendDb ADOdb PDO doctrine propel

Database Lars Jankowfsky,

Database • you might use a database access layer Lars Jankowfsky,

Database • you might use a database access layer • go ORM if you want (performance!) Lars Jankowfsky,

Database • you might use a database access layer • go ORM if you want (performance!) • business layer - not abstraction layer Lars Jankowfsky,

Database • you might use a database access layer • go ORM if you want (performance!) • business layer - not abstraction layer • let‘s call it Data Access Object Lars Jankowfsky,

DB Abstraction Layer PDO, ADOdb, ZendDb....

DB Abstraction Layer PDO, ADOdb, ZendDb.... Table Data Gateway Object Layer Pattern

DB Abstraction Layer PDO, ADOdb, ZendDb.... Table Data Gateway Object Layer Pattern Data Access Object Business Layer

DB Abstraction Layer PDO, ADOdb, ZendDb.... Table Data Gateway Object Layer Pattern Data Access Object Business Layer function giveMeMyData()

Controller Lars Jankowfsky,

Controller • Common mistake: business logic in controller Lars Jankowfsky,

Controller • Common mistake: business logic in controller • Keep it out! Otherwise you will end with SQL in controller Lars Jankowfsky,

Controller • Common mistake: business logic in controller • Keep it out! Otherwise you will end with SQL in controller • I/O mapping to the model and view only Lars Jankowfsky,

Controller • Common mistake: business logic in controller • Keep it out! Otherwise you will end with SQL in controller • I/O mapping to the model and view only • Kick Ass! Lars Jankowfsky,

View Lars Jankowfsky,

View • Use a template engine. Watch performance! Lars Jankowfsky,

View • Use a template engine. Watch performance! • No business logic in the template/html Lars Jankowfsky,

View • Use a template engine. Watch performance! • No business logic in the template/html • Kick Ass! Lars Jankowfsky,

(c) istockphoto

Enforces layered Architecture

use continuous integration e.g. cruise con

Commit frequently.

Unit Tests

Integration Tests Unit Tests

Acceptance Tests Integration Tests Unit Tests

what if ﬁxture/mock preparation are much larger than tests?

what if your tests run for hours ?

(c) istockphoto

framework !== software architecture

evolve your architecture

split your application into layers

enforce proper usage of MVC

wrap database access

utilize test driven development

(c) dasbeibi @ aboutpixel.de

lars.jankowfsky@swoodoo.com Lars Jankowfsky / Thorsten all pictures (c) iStockPhoto if not stated different

Project structure • Remember? Find Boundaries and cut. • quot;Services/Layersquot; - at least on a directory level • use Framework structure • more ??? Lars Jankowfsky,

identify important decisions

scaling? Lars Jankowfsky,

scaling? • web Lars Jankowfsky,

scaling? • web • database Lars Jankowfsky,

scaling? • web • database • services (ext./int.) Lars Jankowfsky,

http://www.frontalaufprall.com	789
http://www.planet-php.net	94
http://jankowfsky.de	52
http://www.jankowfsky.de	32
http://www.slideshare.net	10
http://planet-php.org	9
http://www.open-oxid.com	7
http://www.lars-jankowfsky.de	7
http://www.planet-php.org	6
http://oxid-blog.com	4
http://open-oxid.com	3
http://lj-toys.com	2
http://translate.googleusercontent.com	2
http://web7.my-webspace.eu	1
http://www.netvibes.com	1
http://l33t.0pointer.de	1
http://translate.yandex.net	1
http://lars-jankowfsky.de	1

Why Architecture in Web Development matters

by Lars Jankowfsky on May 27, 2009

Accessibility

Categories

Tags

Upload Details

Usage Rights

18 Embeds 1,022

Statistics

Why Architecture in Web Development matters — Presentation Transcript