Lithium: The Framework for People Who Hate Frameworks, Tokyo Edition

A Framework for People
Who Hate Frameworks.

A movement in 3 parts

• Frameworks suck
• Everything you know is wrong
• Lithium tries to suck less

Let’s get one thing out
of the way:

Because your
framework sucks, too.

Frameworks Suck

• Code you will never use.
• Complexity overhead.
• You didn’t write it.

His name is the
biggest, so it’s his
fault.

We’re not saying design patterns are bad.
Quite the opposite.

Lithium implements many well known design
patterns.

Some patterns only treat the symptoms,
instead of the cause.

Object dependencies.
“The principle of separating configuration from use.”

Sometimes in the same framework.

... but you need to understand what you’re
doing.

Some patterns were implemented in Java, to
solve language problems that PHP just doesn’t
have.

“Design Patterns In Dynamic Languages”
Peter Norvig
http://norvig.com/design-patterns/

The sun does not
revolve around OOP
...nevertheless,
it moves.

Galileo facing the Roman Inquistion
- Cristiano Banti (1857)

Dependency Injection
• Fixes the problem of static dependencies
• Ignores the problem of static relationships
• Same methods called on injected classes
• No way to introduce new relationships
• Higher overhead, more boilerplate code


• Various attempts at making DI work better:
• DI Container
• Using dynamic nature of PHP to your
advantage.

Coupling should be in
proportion to domain
relevance.

If...
Configure::write('debug', 0);

is evil,
$this->debug = 0;

is the

class Service {

protected $_timeout = 30;

public function send($method, $data = null, array $options = array()) {

// WTF does this do?
$this->_prepare();

$response = $this->_connection->send($request, array(
'timeout' => $this->_timeout
));
// ...
}
}

OO doesn’t make you
think (about state).

ActiveRecord
Data Access Object

Unit of Work
Registry

Front Controller MVC

Value Object
Data Mapper Service Layer

Design patterns
• Each pattern is only useful in a limited
context

• Layering many design patterns on top of
each other often indicates poor design
choices

• Mis-application arises from trying to run
before you can walk

Tools do not mean...

...you can build a house.

Aspect-Oriented Design
• Separation of concerns
• Domain classes should not know or care about cross-
cutting concerns

• Examples:
• Caching
• Logging
• Access Control, etc.

Functional Programming

• Only possible when functions are first-class
citizens

• Referential transparency
• Functional purity

Referential transparency is not...

$this date()

$_*

These Are Not
Design Patterns.

Less Suck
• Draws on years of experience building web
frameworks

• PHP 5.3+ only
• Doesn’t assume you’re stupid

<?php

namespace applicationbar;

use lithiumutilString;
use lithiumutilCollection;

class Foo extends lithiumcoreObject {

protected $_classes = array(
'cache' => 'lithiumstorageCache',
'logger' => 'lithiumanalysisLogger'
);

public function __construct(array $config = array()) {
// ...
}

protected function _init() {
// ...
}
}

?>

public function __construct(array $config = array())
<?php


use public function __construct(array $config = array())
lithiumutilString;
public function'lithiumstorageCache', = array())
'cache' => __construct(array $config
);

// ...
}

// ...
}
}
?>

<?php
<?php

class Foo extends lithiumcoreObject
use lithiumutilString; {
$or = $some->highOverHead($operation);
$or()->otherwise(HARD_TO_TEST)->code();
}
}
);

?>
// ...
}

// ...
2
}
}

?>

<?php
<?php

class Foo extends lithiumcoreObject
use lithiumutilString; {
$or = $some->highOverHead($operation);
$or()->otherwise(HARD_TO_TEST)->code();
}
}
);

?>
// ...
}

// ...
2
}
}
$foo = new Foo(array('init' => false));
?>

<?php

namespace applicationbar; 3
new applicationbarFoo();
// loads app/bar/Foo.php

);

// ...
}

// ...
}
}

?>

<?php


4


);

// ...
}

// ...
}
}

?>

<?php




'logger' => 'lithiumanalysisLogger' 5
);

// ...
}

// ... = $this->_classes['cache'];
$cache
} $cache::write(__CLASS__, $this->_someGeneratedValue());
} }
}
?>
?>

<?php




'logger' => 'lithiumanalysisLogger' 5
);

$foo = new Foo(array('classes' => array(
'cache' => 'applicationextensionsCache'
// ...
)));
}

$cache
} }
}
?>
?>

<?php




);

// ...
}

$cache
} }
}
?>
?>

Keeps parameter lists short
&
Makes class APIs more extensible

Same idea. But...!
Modifies class / object state.

Adaptable

Auth

Cache

Catalog

Connections

Logger

Session

use lithiumsecurityAuth;

Auth::config(array(
'customer' => array(
'adapter' => 'Form',
'model' => 'Customer',
'fields' => array('email', 'password')
)
));

use lithiumstorageCache;

Cache::config(array(
'local' => array('adapter' => 'Apc'),
'distributed' => array(
'adapter' => 'Memcached',
'servers' => array('127.0.0.1', 11211),
),
'default' => array('adapter' => 'File')
));

use lithiumdataConnections;

Connections::config(array(
'old' => array(
'type' => 'database',
'adapter' => 'MySql',
'user' => 'bobby_tables',
'password' => '******',
'database' => 'my_app'
),
'new' => array(
'type' => 'MongoDb',
'database' => 'my_app'
)
));

use lithiumstorageSession;

Session::config(array(
'cookie' => array(
'adapter' => 'Cookie',
'expire' => '+2 days'
),
'default' => array('adapter' => 'Php')
));


'default' => array(
'adapter' => 'MyCustomAdapter',
'expires' => '+2 days',
'custom' => 'Whatever!'
)
));

use lithiumstorageCache;

Cache::config(array(
'default' => array(
'development' => array(
'adapter' => 'Apc'
),
'production' => array(
'adapter' => 'Memcached',
'servers' => array('127.0.0.1', 11211)
)
)
));

Works identically for all adapters.

If you remember nothing
else about configuration
state...

Immutability.
Set it and forget it.

Zoom?
• Performance vs. speed of development is a
series of trade-offs

• Large-scale apps don’t use stock framework
infrastructure, and that’s a good thing

• A generalized framework will never be as
fast as hand-tuned code

Zoom!
• Choice is good
• Use native extensions (PECL) whenever
possible.

• Don’t like a class? Change it. At runtime.
• Profiled at every step of the way with
XHProf and XDebug cachegrinds.

use appmodelsPost;
use lithiumactionResponse;
use lithiumnethttpRouter;

Router::connect('/frequent_api_call.json', array(), function($request) {
return new Response(array(
'type' => 'application/json',
'body' => Post::recent()->to('json')
));
});

Platform
Rackspace Cloud
• 256MB ram
• Ubuntu Karmic
• Apache 2.2.12
• PHP 5.3.1
• Xcache
• Siege 2.68

2009-11-26

Lithium is a highly
flexible framework.

Most class dependencies
are dynamic.
(Our implementation of dependency injection)

class Service extends lithiumcoreObject {

'request' => 'lithiumnethttpRequest',
'response' => 'lithiumnethttpResponse',
'socket' => 'lithiumnetsocketContext'
);
}

$service = new Service(array('classes' => array(
'socket' => 'mycustomSocket'
)));

The Filter System:
Aspect-Oriented Design
for PHP.

Example: Caching & Logging

Caching

Logging

Post::find()

use lithiumanalysisLogger;

Post::applyFilter('find', function($self, $params, $chain) {
// Generate the log message
$conditions = $params['options']['conditions'];
$message = 'Post query with constraint ' . var_export($conditions, true);

Logger::write('info', $message);
return $chain->next($self, $params, $chain);
});

use lithiumanalysisLogger;

Post Logger
Post::applyFilter('find', function($self, $params, $chain) {
// Generate the log message
$conditions = $params['options']['conditions'];
$message = 'Post query with constraint ' . var_export($conditions, true);

Logger::write('info', $message);
return $chain->next($self, $params, $chain);
});

What about Observer?

• Dependent on a centralized publish/
subscribe system

• Extra layer of abstraction
• Fewer possibilities

What about Observer?

• Filters are self-contained and attach
directly to objects

• Direct and intuitive

Features: Everything is an adapter.

(well, almost)

Databases
• 1st-class support for document-oriented
databases

• MongoDB & CouchDB: production ready
• Relational databases in beta
• Cassandra/Redis/Riak in the works, too

<?php

$post = Post::create(array(
'title' => ' ',
'body' => ' '
));
$post->save();

$post = Post::find($id);

?>

<h2><?=$post->title; ?></h2>
<p><?=$post->body; ?></p>

This works on...

• MongoDB
• CouchDB
• MySQL
• SQLite

MongoDB + CouchDB:
$post = Post::create(array(
'title' => ' ',
'body' => ' ',
'tags' => array('PHP', 'Japan'),
'author' => array('name' => 'Nate')
));

$post->save();

MongoDB:
$posts = Post::all(array('conditions' => array(
'tags' => array('PHP', 'Japan'),
'author.name' => 'Nate'
)));

// Translates to...
db.posts.find({
tags : { $in : ['PHP', 'Japan'] },
'author.name' : 'Nate'
})

Databases

• Adapter based, plugin aware
• Will ship with MySQL, SQLite & PostgreSQL
• SQL Server support via plugin
• Query API

The Query API

• Flexible data container
• Allows each backend data store to only worry
about features it implements

• Keeps model API separate from backend data
sources

The Query API

$ages = User::all(array(
'group' => 'age',
'reduce' => 'function(obj, prev) { prev.count++; }',
'initial' => array('count' => 0)
));

The Query API
$query = new Query(array(
'type' => 'read',
'model' => 'appmodelsPost',
'fields' => array('Post.title', 'Post.body'),
'conditions' => array('Post.id' => new Query(array(
'type' => 'read',
'fields' => array('post_id'),
'model' => 'appmodelsTagging',
'conditions' => array('Tag.name' => array('foo', 'bar', 'baz')),
)))
));

The Query API

• Run simple queries via the Model API
• Build your own complex queries with the
Query API

• Create your own adapter, or drop in a
custom query optimizer

Plays nice with others

• Easily load & use libraries from other
frameworks:

• Zend Framework, Solar, Symfony, PEAR,
etc.

• PSR-0 Class-loading standard

/* add the trunk */
Libraries::add("Zend", array(
"prefix" => "Zend_",
"includePath" => true,
"bootstrap" => "Loader/Autoloader.php",
"loader" => array("Zend_Loader_Autoloader", "autoload"),
"transform" => function($class) { return str_replace("_", "/", $class) . ".php"; }
));

/* add the incubator */
Libraries::add("Zend_Incubator", array(
"prefix" => "Zend_",
"includePath" => '/htdocs/libraries/Zend/incubator/library',
"transform" => function($class) { return str_replace("_", "/", $class) . ".php"; }
));

namespace appcontrollers;

use Zend_Mail_Storage_Pop3;

class EmailController extends lithiumactionController {

public function index() {
$mail = new Zend_Mail_Storage_Pop3(array(
'host' => 'localhost', 'user' => 'test', 'password' => 'test'
));
return compact('mail');
}

}

This has been a presentation by:

Nate Abele (@nateabele)

Joël Perras (@jperras)

http://lithify.me
Sucks. But check it out anyway.

Lithium: The Framework for People Who Hate Frameworks, Tokyo Edition

More Related Content

What's hot (20)

Viewers also liked (7)

Similar to Lithium: The Framework for People Who Hate Frameworks, Tokyo Edition (20)

Recently uploaded (20)

Lithium: The Framework for People Who Hate Frameworks, Tokyo Edition