Moving to a service oriented architecture from tightly coupled applicationsi xavier briand
31
Xavier Briand Senior Web Application Developer ExperiencePoint Inc (please excuse my accent)
-
Upload
xavier-briand -
Category
Technology
-
view
256 -
download
0
description
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.
Transcript of Moving to a service oriented architecture from tightly coupled applicationsi xavier briand
Xavier BriandSenior Web Application Developer
ExperiencePoint Inc
(please excuse my accent)
Moving to aService Oriented Architecture
from tightly coupledapplications
ExperiencePoint"The best way to learn is to experience."
Business
(1+½)+(4+3) simulations
Previous Architecture
Problemstightly coupled applications
no dependency management
no tests
deprecated technologies
1 dev symptoms
2 environments
SVN
ExperienceChange Model
Meet the dev team
Step 1
Reset ðGoal: efficient dev environment
VM
Modern SCM
Modern Frameworks
Tasks automation
Problem
Dependency management
logo: WizardCat
$ make build
{ "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, 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, validate Validates a composer.json
Problem
App config managementcomposer (Platform packages)
incenteev/composer-parameter-handler$ make build
Step 2
“Defeat in detail”Divide and gather (DRY)
Keep things small + KISS
Design by contract
Leverage your architecture
Opportunity: GlobalTech
InsideRemove Flash... No! Ok but:
Let’s use the best technologyto do the job
AMF => plain HTTP via browser
Business Logic => Backend
Frontend UI => Flash
Hypermedia API> POST /games/ + content
< 201 Created < Location /games/1
> GET /games/1
< 200 Ok < < <game> < <!-- ... --> < <links rel=”actionX” src=”...”></links> < <links rel=”actionY” src=”...”></links> < </game>
David Zuelke "Designing HTTP Interfaces and RESTful Web Services"
Globally
Implementation
Strategy Pattern
Solutions
OAuth2
Solutions
Backend App API
Solutions
Product API
The other way around
Step 3
ConsolidateBackendAppSdkBundle
OAuth2ClientBundle
ApiBundle
AssetsBundle
Rinse and repeat...
Step 4
Plan for the futur
Question? (four 9)joind.in/9999
Symfony
We are hiring!experiencepoint.com/careers
