Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
From 1 to 20 million users the technical story of BlaBlaCar
Search
Matthieu Moquet
June 06, 2015
Programming
1
1.7k
From 1 to 20 million users the technical story of BlaBlaCar
IPC Spring Berlin 2015
Matthieu Moquet
June 06, 2015
Tweet
Share
More Decks by Matthieu Moquet
See All by Matthieu Moquet
Migrating to containers
mattketmo
0
340
CQRS & Event Sourcing — LavaJUG
mattketmo
1
470
Running container at BlaBlaCar — While 42 (San-Francisco)
mattketmo
0
350
ForumPHP 2015
mattketmo
0
790
CQRS & Event Sourcing
mattketmo
7
1.3k
Take care of your logs with ELK
mattketmo
8
670
Event Sourcing
mattketmo
9
3.8k
Localization should not be a pain (anymore)
mattketmo
1
700
Understanding git
mattketmo
5
590
Other Decks in Programming
See All in Programming
小さな開発会社を作った理由
polidog
0
1.9k
CSC307 Lecture 12
javiergs
PRO
0
220
みんなのオブザーバビリティプラットフォームを作ってるんだがパフォーマンスがやばい #mackerelio #srenext
ne_sachirou
0
380
Findy - エンジニア向け会社紹介 / Findy Letter for Engineers
findyinc
2
81k
入社1ヶ月でここまでやった!Findy Toolsインフラ支援の最適化
rvirus0817
6
1.4k
【Go言語】golangci-lintの使い方
tomo1227
0
280
ドメイン駆動設計の実践
masuda220
PRO
19
5.2k
Javaの現状2024夏 / Java current status 2024 summer
kishida
4
1.4k
20240706_CDKConf
takuyay0ne
0
1.2k
CSC307 Lecture 08
javiergs
PRO
0
330
開発部に不満を持っていたCSがエンジニアにジョブチェンしてわかった「勝手に諦めない」ことの大切さ
sakuraikotone
28
16k
12年前の『型システム入門』翻訳の思い出話
mame
11
1.2k
Featured
See All Featured
Testing 201, or: Great Expectations
jmmastey
33
6.9k
For a Future-Friendly Web
brad_frost
173
9.2k
What’s in a name? Adding method to the madness
productmarketing
PRO
21
2.9k
Building Flexible Design Systems
yeseniaperezcruz
323
37k
Gamification - CAS2011
davidbonilla
78
4.9k
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
325
21k
A Tale of Four Properties
chriscoyier
155
22k
Leading Effective Engineering Teams 2024
addyosmani
3
300
Large-scale JavaScript Application Architecture
addyosmani
506
110k
A designer walks into a library…
pauljervisheath
201
24k
Dealing with People You Can't Stand - Big Design 2015
cassininazir
360
22k
ピンチをチャンスに:未来をつくるプロダクトロードマップ #pmconf2020
aki_iinuma
90
47k
Transcript
the technical story of From 1 to 20 million users
Matthieu Moquet @MattKetmo web engineer at
Leader ride-sharing service Our goal is to become the 1st
travel platform
Why this talk? ❖ History of the BlaBlaCar platform ❖
Overview our main technical choices ❖ Understand of our culture & methodologies
v1.0 2005–2006
The prototype
v2.0 (2008) – Plain PHP
2008 2010 2011 2012 v2.0
None
None
Homemade framework + No code convention + Messy = Not
maintainable in the long term
$ wc -‐l lib.trip.php Longest method: 1000+ lines 3678
None
No tests
Going further will be a pain Hiring will be hard
We need to change things
Refactor all the code
Symfony 2.0
Because community matters
Attract new talented & motivated people
Separation of Concerns Dependencies Injection Integration & Unit tests etc.
Embrace best practices
Update product design
None
Agility is our best strength
— Eberhardt Von Kuenheim « The big will not always
eat the small, but the fast ones will overtake the slow ones »
10+ deployments per day
DEVOPS… before it was cool « if you break it
you fix it »
Automation Automatize as much as possible to reduce the time
between dev and prod
Simple development workflow Master Branch
git push origin feat-awesome Deploy on staging environment is as
simple as
Staging env. for QA & product owners https://feat-awesome.staging.blablacar.com
Continuous Integration https://github.com/alexandresalome/behat-launcher
None
Localization Update translations on the fly
Frontend server Databases Backoffice Sync translations Update translations
Download last translations when app boot Update translations Mobile app
CDN Backoffice
openl10n.io
Progressive Rollout ❖ Open new countries with v3 one by
one ❖ It took about 2.5 years to run v3 everywhere ❖ Today we can deploy new features for a set of users (by attributes or random)
Monitoring
ELK
Monitoring
Departure to new horizons…
Opportunity to change backend But we still keep the same
primary database
Database Updates Sync replication & No Master SPOF
Better archiving strategy
Photo Storage Don’t store static BLOB into MySQL. Use an
elastic filesystem storage. MySQL AWS S3
elasticsearch ❖ Horizontally scalable ❖ Geo type index ❖ Aggregations
Varnish Fast reverse proxy cache 30% HIT/MISS Firemode to handle
high traffic (TTL) Be careful with authenticated user blocks (Javascript is your friend)
SPDY (HTTP 2.0) Fast API calls for (compliant) mobile clients
ngx_http_spdy_module
Asynchronous jobs Command Command Handlers Commands Queueing Ack
workers/ mail sms push
image-‐resize indexer cache-‐invalidation elasticsearch-‐indexation trip-‐publication ... github.com/swarrot
Horizontal scalability
Event dispatcher Every business events is dispatched into RabbitMQ Easy
to watch the events (in real-time or batchs)
Data Warehouse Log every business event into Hadoop user.register user.edit_bio
user.left_rating user.post_trip ...
user.register user.edit_bio user.left_rating user.post_trip ... user.register user.post_trip ... Real-Time dashboard
Log every business event into Elasticsearch
Such performances. Many users. Wow.
How to serve the product worldwide?
Datacenter centric One datastore to rule them all? It ain’t
gonna work. ?? ??
Monolithics Micro-Services
Today we are mainly Monolithics But we would love using
more Micro-Services Easier to deploy Development workflow Legacy database Smaller teams Faster deployments Easier to scale out
Gateway Principles (Clean Architecture) Decouple models (not db) Isolate business
& data accesses (in the Monolytics to better decouple in micro services) Restrictive rules Enter the
Gateway RegisterUser PublishTrip PostMessage UpdateBio PostRating Users Messages Trips Business
Data
But this is a long term project…
caching In the short term we invested on
Points of presence & Varnish
Mobile First
But how to cache the API? GET /api/trips?from=Paris&to=Berlin Authorization:
Bearer 7c82e855b0415f27bd92d HTTP/1.1 200 OK { "trips": [...] }
{ Reverse proxy is useless if only the app knows
the authorizations Reverse Proxy Client User Scopes Access Token
Let the reverse proxy check authorization directly Reverse Proxy But
here is a latency problem
Use of stateless token Reverse Proxy So we don’t need
a database anymore
Json Web Token
What mobile apps send GET /api/trips?from=Paris&to=Berlin Authorization: Bearer eyJhbGciOiJIUzI1NiI...
What backend servers receive GET /api/trips?from=Paris&to=Berlin X-‐Auth-‐User: 1337
X-‐Auth-‐Client: android X-‐Auth-‐Scope: user_info,messages
App gets an Access Token from the origin Reverse Proxy
App submit request with Access Token Reverse Proxy transform Access Token header into custom X-Auth headers
Cachable response HTTP/1.1 200 OK Content-‐Type application/json Vary:
X-‐Auth-‐Scope ! { "trips": [ ... ] }
Long term solution to deliver data close to the client
❖ Manage massive amounts of data ❖ High Availability ❖
Multi Datacenter replication
‣ Know the read requests before creating your data models
‣ Create as many tables (KeySpaces) than you have views ‣ Denormalize the data (no join allowed)
CQRS & Event Sourcing ❖ Separate Read & Write ❖
Eventual consistency ❖ But hard to do with legacy software / database See talk PHPTour 2015 at moquet.net
C* C* C* Primary Data C* Read Data User post
message Endpoint
Messaging (micro) service Expose an HTTP API
2008 2012 2013 2014 2015 2016 2 6 15 30+
… ?
blablatech.com We’re hiring Follow us
Thank You Slides available at moquet.net/talks/ipc-2015-blablacar Leave feedbacks at @MattKetmo