Xavier Br iand
Senior Web Application Developer
ExperiencePoint Inc
(please excuse my accent)
SensioLabs trainings/coaching
not only for the amazing styles
Moving to a
ExperiencePoint
"The best way to learn is to experience."
21 employees
Business
(1+½)+(4+3) simulations
Frontend App
Previous Architecture
Old: All symfony1.0 app (created in 2005, end of support jan 2010 (symfony1.4 november 2012))
Problems
tightly coupled applications
no dependency management
no tests
deprecated technologies
1 dev symptoms
2 environments
SVN
manage the existant while migrating, no big switch to convert everything
ExperienceChange Model
internal culture teaches use this
Meet the dev team
+ 2 designers
Step 1
Reset ⟲
Goal: efficient dev environment
VM
Modern SCM
Modern Frameworks
Tasks automation
VM: FreeBSD jails (can be cloned, saved, restored) => consistent dev env while keeping dev in different env. Can achieve prod = dev
Problem
Dependency management
logo: WizardCat
$ make build
Composer
As easy as adding a package.json file
{
"name " : "ep/ec" license " : "proprietary" autoload " : {
"psr-0 ": { ""src/" } ,
"require ": {
"php " : ">=5.3.3" symfony/symfony " : "~2.4" doctrine/orm " : "~2.2,>=2.2.3" ep/backend-sdk-bundle " : "dev-master" ep/old-stuff " : "dev-trunk"
} ,
"require-dev ": {
"phpunit/phpunit ": "3.7.*"
}
$ php composer.phar
______
/ ____/___ ____ ___ ____ ____ ________ _____
/ / / __ \/ __ `__ \/ __ \/ __ \/ ___/ _ \/ ___/
/ /___/ /_/ / / / / / / /_/ / /_/ (__ ) __/ /
\____/\____/_/ /_/ /_/ .___/\____/____/\___/_/
/_/
Available commands:
install Installs the project dependencies from the composer.lock file if present, or falls back on the composer.json.
require Adds required packages to your composer.json and installs them
search Search for packages
self-update Updates composer.phar to the latest version.
status Show a list of locally modified packages
update Updates your dependencies to the latest version according to composer.json, and updates the composer.lock file.
validate Validates a composer.json
Problem
App config management
composer (Platform packages)
incenteev/composer-parameter-handler
$ make build
Application should be unaware of physical environment details, but should provide requirements.
Problem
QA
$ make prepare analysis
check style
Step 2
“Defeat in detail”
Divide and gather (DRY)
Keep things small + KISS
Design by contract
Leverage your architecture
Where there code duplication there is an opportunity to gather this code and create a new module\
Opportunity: GlobalTech
From scratch, Sf2 + Flex
Inside
Remove Flash... No! Ok but:
Let’s use the best technology
AMF => plain HTTP via browser
Business Logic => Backend
Frontend UI => Flash
Hypermedia API
> POST /games/ + content
> GET /games/1
David Zuelke "Designing HTTP Interfaces and RESTful Web Services"
The HATEOAS constraint serves to decouple client and server in a way that allows the server to evolve functionality independently,
Globally
Delegate session logic
Implementation
Strategy Pattern
Old applications need to know when delegate new features: Array of enabled products
Solutions
OAuth2
Shared auth between Frontend app and Auth app
Solutions
Backend App API
Standalone application
Solutions
Product API
Serve data and reports to Frontend and Backend App
The other way around
Product options: Remove every simulation details from Backend App
Step 3
Consolidate
BackendAppSdkBundle
OAuth2ClientBundle
ApiBundle
AssetsBundle
Rinse and repeat...
What do you do before starting a new project? refactoring refactoring
Step 4
Plan for the futur
wrapping old app into sf2 (session bridge)
Question?
joind.in/9999 (four 9)
Symfony
Symfony Toronto Meetup group
