Data Abstraction for Large Web Applications

Data Abstraction for
Large Web Applications
By Brandon Savage

Who Am I?

• Software developer at Mozilla working on Socorro

• Author of the PHP Playbook

• Former frequent blogger on PHP topics

• Private pilot in my spare time

Data Abstraction For LARGE
Web Applications

Once upon a time...

In a galaxy far far away...

Eventually the web grew up.

And grew larger.

Most webapps still start as
though they’ll always use a
database.

We need to change our
thinking.

Socorro Data Sources
• Postgres

• REST API (Middleware)

• Elastic Search

• Hbase

• Bugzilla REST API

• Memcache

A database-centric model just
doesn’t work anymore.

Solving the problem

• Separate the use of data from the retrieval of data.

• Think in terms of actions.

• Build our applications to be storage agnostic.

• Use the correct data storage medium.

#1 Separate the use of data
from the retrieval of data

<?php
class MainPage_Controller {
/* ... */
public function do_something(){
/* ... */
$sql = ‘SELECT * FROM database”;
$results = $this->execute($sql);
return $this->executeView(‘index’, array(‘results’ => $results));
}
}

<?php
class Data_Model {
/* ... */
public function get_some_data() {
$sql = ‘SELECT * FROM database”;
$results = $this->execute($sql);
/** process results **/
return $processedResults
}
}

Processing the data is a
separate layer.

<?php
class Data_Model {
/* ... */
public function getSomeData() {
$data = $this->adapter->queryData();
! /** process data here **/
! return $processedData;
}
}

class Data_Model_Adapter extends MySQL_Adapter implements Adapter
{
public function queryData() {
$sql = ‘SELECT * FROM table’;
/** turn into common format **/
return $commonFormatData;
}
}

Swapping out data sources
becomes very simple.

Make life easier on yourself: do
it right the ﬁrst time!

Actions move beyond SELECT,
INSERT, UPDATE and DELETE.

Domain Modeling:
“What are you modeling?”

What do I want?
What do I need?
What does this data represent?

Django Models:
One model per table.
All methods relate to SQL.
That sucks.

<?php
abstract class User_Model {

public function loadUser();

public function authenticateUser();

public function showUserPhones();

}

#3 Build our applications to be
storage agnostic

Create custom objects for
typehinting or additional
methods

Avoid expecting built-ins like
PDOStatement and
MongoCursor outside
retrieval layer

#4 Use the correct
storage medium.

Example: memcache isn’t for
long-term storage.

Example: MongoDB is not for
relational data storage.

Relational data goes in relational
databases!

Choose the correct NoSQL
database for your needs.

Availability, reliability, and
consistency.

Pick two.

Consider data storage that isn’t
a database at all.

Alternative data options

• Elastic Search

• Redis

• S3

• The File System (Yes! It still exists!)

Fix it now or ﬁx it later.

But you will have to ﬁx it.

Data Abstraction for Large Web Applications

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to Data Abstraction for Large Web Applications (20)

Recently uploaded (20)

Data Abstraction for Large Web Applications

Editor's Notes