Lessons from a year of rearchitecting tightly coupled 4-year-old applications to a SOA while keeping developers happy (for the most part). For a year, ExperiencePoint's development team has been rebuilding its aging applications to a modern and highly available architecture. We have been able to spend more time on developing our new products while reducing our technological debt by building on top of standard technologies, separating concerns and automating our working environment. This talk will show the benefits of splitting omniscient applications to smaller independent modules and explain why your web applications should use HTTP RESTful API to communicate with each other. We'll also explore a few strategies to deal with aging PHP applications or deprecated technologies.

1. Xavier Briand
Senior Web Application Developer
ExperiencePoint Inc
(please excuse my accent)

3. mobro.co/xavierbriand

4. Moving to a
Service Oriented Architecture
from tightly coupled
applications

5. ExperiencePoint
"The best way to learn is to experience."

6. Business
(1+½)+(4+3) simulations

9. Previous Architecture

10. Problems
tightly coupled applications
no dependency management
no tests
deprecated technologies
1 dev symptoms
2 environments
SVN

11. ExperienceChange Model

12. Meet the dev team

13. Step 1
ð
Reset
Goal: efficient dev environment
VM
Modern SCM
Modern Frameworks
Tasks automation

14. Problem
Dependency management
logo: WizardCat
$mk bid
ae ul

15. {
"ae
nm"
:"pe"
e/c,
"ies" :"rpitr"
lcne
poreay,
"uood :{
atla"
"s-" {":"r/ }
pr0:
" sc"
}
,
"eur" {
rqie:
"h"
pp
:"=.."
>533,
"yfn/yfn"
smoysmoy
:"24,
~."
"otieom
dcrn/r"
:"22>223,
~.,=.."
"pbcedskbnl":"e-atr,
e/akn-d-ude
dvmse"
"podsuf
e/l-tf"
:"e-rn"
dvtuk
}
,
"eur-e" {
rqiedv:
"hui/hui" ".."
ppntppnt: 37*
}
}

16. $ppcmoe.hr
h opsrpa
___
___
/__/_ __ __ __ __ ____ ___
____ __ _
__ __ ____ __
// /_ _ `_ _ _ __ _ __
_ / _ _ / _ / _ / _/
/ _/
//_//////////////(_ ) _//
__ _
_
_ _
_
_____ ////._/__/___//
__/__// _ _ ______/___
//
_
Aalbecmad:
vial omns
isal
ntl
Isal tepoetdpnece fo tecmoe.okfl i pee
ntls h rjc eednis rm h opsrlc ie f rs
rqie
eur
Ad rqie pcae t yu cmoe.snadisal te
ds eurd akgs o or opsrjo n ntls hm
sac
erh
Sac frpcae
erh o akgs
sl-pae
efudt
Udtscmoe.hrt telts vrin
pae opsrpa o h aet eso.
sau
tts
So als o lclymdfe pcae
hw
it f oal oiid akgs
udt
pae
Udtsyu dpnece t telts vrinacrigt cmoe.
pae or eednis o h aet eso codn o opsr
vldt
aiae
Vldtsacmoe.sn
aiae
opsrjo

17. Problem
App config management
cmoe (ltompcae)
opsr Pafr akgs
icnevcmoe-aaee-ade
nete/opsrprmtrhnlr
$mk bid
ae ul

18. Problem
QA
+
jenkins-php.org
$mk peaeaayi
ae rpr nlss

19. Step 2
“Defeat in detail”
Divide and gather (DRY)
Keep things small + KISS
Design by contract
Leverage your architecture

20. Opportunity: GlobalTech

21. Inside
Remove Flash... No! Ok but:
Let’s use the best technology
to do the job
AMF => plain HTTP via browser
Business Logic => Backend
Frontend UI => Flash

22. Hypermedia API
>PS /ae/+cnet
OT gms
otn
<21Cetd
0 rae
<Lcto /ae/
oain gms1
>GT/ae/
E gms1
<20O
0 k
<
<<ae
gm>
<
<- ..->
!- . <
<ik rl”cin”sc”.”<lns
lns e=atoX r=..>/ik>
<
<ik rl”cin”sc”.”<lns
lns e=atoY r=..>/ik>
<<gm>
/ae
David Zuelke "Designing HTTP Interfaces and RESTful Web Services"

23. Globally

24. Implementation
Strategy Pattern

25. Solutions
OAuth2

26. Solutions
Backend App API

27. Solutions
Product API

28. The other way around

29. Step 3
Consolidate
BackendAppSdkBundle
OAuth2ClientBundle
ApiBundle
AssetsBundle
Rinse and repeat...

30. Step 4
Plan for the futur

31. Question?
joind.in/9999 (four 9)
Symfony
We are hiring!
experiencepoint.com/careers