Live On Stage

Live on
Stage
Dominik Jungowski - May 14, 2010

Live on Stage - Dominik Jungowski

Agenda

2


Agenda
‣ What is Staging?

2


Agenda

‣ Reasons for Staging

2


Agenda


‣ Implementation

2


Agenda


‣ Implementation

‣ Adding a staging layer

2


Agenda


‣ Implementation

‣ Adding a staging layer

‣ Problems and Solutions
2


About me

3


About me
‣ 25 years old

3


About me
‣ 25 years old
‣ Employed at CHIP Xonio Online GmbH

3


About me
‣ 25 years old
➡ www.chip.de

3


About me
‣ 25 years old
➡ www.chip.de

➡ download.chip.eu

3


About me
‣ 25 years old
➡ www.chip.de


‣ ScrumMaster and Developer at price
comparison

3


About me
‣ 25 years old
➡ www.chip.de


‣ ScrumMaster and Developer at price
comparison
‣ Part - time studies in Psychology at distance
university FernUni Hagen

3


What is
staging?


What is Staging?
Usual Database Design:

5


What is Staging?

Databa

5


What is Staging?

Databa

Website

5


What is Staging?

Databa

Website Admin

5


What is Staging?
Staging Database Design:

6


What is Staging?

Databa

6


What is Staging?

Databa

Website

6


What is Staging?

Databa Databa

Website

6


What is Staging?

Databa Databa

Website Admin

6


What is Staging?

Databa Sync Databa

Website Admin

6


Reasons for
staging


Reasons for Staging

8


Reasons for Staging
‣ Security

8


Reasons for Staging
‣ Security
➡ no sensitive data on live system

8


Reasons for Staging
‣ Security

➡ only the essential data is synced

8


Reasons for Staging
‣ Security


‣ Quality

8


Reasons for Staging
‣ Security


‣ Quality
➡ no changes directly on live system

8


Reasons for Staging
‣ Security


‣ Quality
➡ no changes directly on live system

➡ more time to prevent corruption/errors on live
system (user errors, broken imports, etc.)

8


Reasons for Staging
‣ Performance

9


Reasons for Staging
‣ Performance
➡ Normalized data on staging database

9


Reasons for Staging
‣ Performance

➡ Performance optimized / ﬂat data on live database

9


Reasons for Staging
‣ Performance

➡ Performance optimized / ﬂat data on live database

➡ no constraints on live system possible

9


Implementat
ion


Implementation

11


Implementation
‣ Data is synced

11


Implementation
‣ Data is synced
➡ some kind of status ﬂag in staging db is needed

11


Implementation
‣ Data is synced

‣ Status needed for

11


Implementation
‣ Data is synced

➡ Changed data

11


Implementation
‣ Data is synced

➡ Changed data

➡ Unchanged data

11


Implementation
‣ Data is synced

➡ Changed data

➡ Unchanged data

➡ Deleted data on staging, but not on live system

11


Implementation
‣ Data is synced

➡ Changed data

➡ Unchanged data


‣ Maybe useful

11


Implementation
‣ Data is synced

➡ Changed data

➡ Unchanged data


‣ Maybe useful
➡ Deleted on live system

11


Implementation
The Status - Cycle

12


Implementation
The Status - Cycle

Import

12


Implementation
The Status - Cycle

ne
w or
ch
an
ge
dd
ata

Import

12


Implementation
The Status - Cycle

Changed
[1]
ne
w or
ch
an
ge
dd
ata

Import

12


Implementation
The Status - Cycle

Changed
[1]
ne
w or
ch
an
ge
dd
ata
Sync

Import

12


Implementation
The Status - Cycle

Changed
[1]
ne
w or
ch
an
ge
dd
ata
Sync

Import

No
change
[0]

12


Implementation
The Status - Cycle

Changed
[1]
ne
w or
ch
an
ge
dd
ata
Sync

Import
rem
ov
ed
da
ta

No
change
[0]

12


Implementation
The Status - Cycle

Changed
[1]
ne
w or
ch
an
ge
dd
ata
Sync

Import
rem
ov
ed
da
ta

No Changed
change Deleted
[0] [3]

12


Implementation
The Status - Cycle

Changed
[1]
ne
w or
ch
an
ge
dd
ata
Sync

Sync
Import
rem
ov
ed
da
ta

No Changed
change Deleted
[0] [3]

12


Implementation
The Status - Cycle

Changed Deleted
[1] [2]
ne
w or
ch
an
ge
dd
ata
Sync

Sync
Import
rem
ov
ed
da
ta

No Changed
change Deleted
[0] [3]

12


Implementation

Why 0, 1, 2,
3?


Implementation

Why 0, 1, 2,
3?
Let‘s take a look at the binary
numbers!


Implementation

14


Implementation
No
change
[0]

14


Implementation
No
change
[0]
=

14


Implementation
No
change
[0]
= 0000

14


Implementation
No
change
[0]
= 0000

Changed
[1]

14


Implementation
No
change
[0]
= 0000

Changed
[1] =

14


Implementation
No
change
[0]
= 0000

Changed
[1] = 0001

14


Implementation
No
change
[0]
= 0000

Changed
[1] = 0001

Deleted
[2]

14


Implementation
No
change
[0]
= 0000

Changed
[1] = 0001

Deleted
[2] =

14


Implementation
No
change
[0]
= 0000

Changed
[1] = 0001

Deleted
[2] = 0010

14


Implementation
No
change
[0]
= 0000

Changed
[1] = 0001

Deleted
[2] = 0010
Changed
Deleted
[3]
14


Implementation
No
change
[0]
= 0000

Changed
[1] = 0001

Deleted
[2] = 0010
Changed
Deleted
[3]
=
14


Implementation
No
change
[0]
= 0000

Changed
[1] = 0001

Deleted
[2] = 0010
Changed
Deleted
[3]
= 0011
14


Implementation
No
change
[0]
= 0000

Changed
[1] = 0001

Deleted
[2] = 0010
Changed
Deleted
[3]
= 0011
= 0001 | 0010
14


Implementation
Using the binary ﬂags in PHP
class phpDay_Sync
{
/**
* Status for changed data
* Binary: 0001
*/
const STATUS_CHANGED = 1;

/**
* Status for removed data
* Binary: 0010
*/
const STATUS_DELETED = 2;

...
}
15


Implementation

16


Implementation
// Speaker status has changed

16


Implementation
$speaker[‘status‘] = phpDay_Sync::STATUS_CHANGED;

16


Implementation

// Speaker has been synced to live system

16


Implementation

$speaker[‘status‘] =

16


Implementation

(phpDay_Sync::STATUS_CHANGED &
phpDay_Sync::STATUS_DELETED);

16


Implementation


//... or easier :-)

16


Implementation


//... or easier :-)
$speaker[‘status‘] = 0;

16


Implementation

17


Implementation
// Speaker didn‘t show up in import ﬁle

17


Implementation
// 0001 | 0010 = 0011

17


Implementation
// 0001 | 0010 = 0011
(phpDay_Sync::STATUS_CHANGED |

17


Implementation
// 0001 | 0010 = 0011

// Speaker has been deleted on live system

17


Implementation
// 0001 | 0010 = 0011

// Speaker has been deleted on live system
$speaker[‘status‘] = phpDay_Sync::STATUS_DELETED;

17


Binary AND
& 0 1 2 3

0 0 0 0

1 0 0 1

2 0 0 2

3 0 1 2
18


Binary AND
& 0 1 2 3
0000 0000 0000
0 & 0001 & 0010 & 0011
= 0000 = 0000 = 0000
0001 0001 0001
1 & 0000 & 0010 & 0011
= 0000 = 0000 = 0001
0010 0010 0010
2 & 0000 & 0001 & 0011
= 0000 = 0000 = 0010
0011 0011 0010
3 & 0000 & 0001 & 0011
= 0000 = 0001 = 0010
19


Binary OR
| 0 1 2 3

0 1 2 3

1 1 3 3

2 2 3 3

3 3 3 3
20


Binary OR
| 0 1 2 3
0000 0000 0000
0 | 0001 | 0010 | 0011
= 0001 = 0010 = 0011
0001 0001 0001
1 | 0000 | 0010 | 0011
= 0001 = 0011 = 0011
0010 0001 0010
2 | 0000 | 0010 | 0011
= 0010 = 0011 = 0011
0011 0011 0011
3 | 0000 | 0001 | 0010
= 0010 = 0011 = 0011
21


Deleting on live
system
Status 3 Status 2


Implementation
& 0 1 2 3

0 0 0 0

1 0 0 1

2 0 0 2

3 0 1 2
23


Implementation
... in PHP

24


Implementation
... in PHP
// We‘ve synced the deleted speaker, status 3 => status 2

24


Implementation
... in PHP
// 0011 & 0010 = 0010

24


Implementation
... in PHP
// 0011 & 0010 = 0010
($speaker[‘status‘] & phpDay_Sync::STATUS_DELETED);

24


Implementation
... in PHP
// 0011 & 0010 = 0010

// or if you know you will never use more than those 4 status ﬂags:

24


Implementation
... in PHP
// 0011 & 0010 = 0010

// or if you know you will never use more than those 4 status ﬂags:
$speaker[‘status‘] = phpDay_Sync::STATUS_CHANGEDELETED;

24


Implementation
... in MySQL

25


Implementation
... in MySQL
// 0011 & 0010 = 0010
$sql =
‘UPDATE speaker SET status = status & ‘ .
phpDay_Sync::STATUS_DELETED;

25


Implementation
... in MySQL
// 0011 & 0010 = 0010
$sql =
‣ But: Rather slow in MySQL

25


Implementation
... in MySQL
// 0011 & 0010 = 0010
$sql =
‣ But: Rather slow in MySQL
// 0011 & 0010 = 0010
$status = $speaker->getStatus();
$sql =
‘UPDATE speaker SET status = ‘ . ($status &

25


Adding a staging
layer
Things to consider


Adding a staging layer

27


‣ Distribution of cronjobs: 1 server ➝ 2 servers

27


➡ Data you need on live system

27



➡ Data you need on staging system

27




➡ Data you need on both systems

27





‣ Write down all the cronjobs

27





‣ Write down all the cronjobs
‣ Decide where you need them

27


‣ Switching live system

28



Database
server

28



Old database
Database
server

28



Old database
Database
server
New (synced)
database

28



Old database
Database
Website server
New (synced)
database

28


Problems &
Solutions

29


Problems & Solutions
‣ Problem: Data integrity

30



Status
ﬂag

30



Read for
Sync

Status
ﬂag

30



Read for
Sync
St
at
us
:1

Status
ﬂag

30



Read for User
Sync
St
at
us
:1

Status
ﬂag

30



Read for User
Sync

Status: 1
St
at
us
:1

Status
ﬂag

30



Read for Sync
User
Sync ﬁnished

Status: 1
St
at
us
:1

Status
ﬂag

30



Read for Sync
User
Sync ﬁnished

0
Status: 1
St

s:
at

u
at
us

St
:1

Status
ﬂag

30



31


‣ Solution: Table locking

31


mysql> LOCK TABLES speaker WRITE;

31



‣ Problem: Whole table is locked for reading and
writing

31



writing
mysql> SELECT * FROM speaker WHERE status = 1 FOR UPDATE;

31



writing

‣ Only locks the selected rows

31



writing

‣ Only locks the selected rows
‣ Reading other data from table is still possible

31


Contact me
‣ Weblog: www.phpdevblog.net

‣ Twitter: www.twitter.com/djungowski

‣ Xing: http://www.xing.com/proﬁle/
Dominik_Jungowski

32


Questions?

33


Thank you!

34


Live On Stage

Recommandé

Recommandé

Contenu connexe

Plus de Dominik Jungowski

Plus de Dominik Jungowski (20)

Dernier

Dernier (20)

Live On Stage

Notes de l'éditeur