Slicing up a monolithic application Why and how?

Slide 1

Slide 1 text

Slide 2

Slide 2 text

No content

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

No content

Slide 5

Slide 5 text

Slicing up a monolithic application Why and how?

Slide 6

Slide 6 text

What is a monolithic application?

Slide 7

Slide 7 text

“It does everything, even coffee” - Every developer ever

Slide 8

Slide 8 text

Website

Slide 9

Slide 9 text

Mobile apps

Slide 10

Slide 10 text

So big!

Slide 11

Slide 11 text

406 187 NLOC There are “only” 268 041 NLOC for symfony/symfony

Slide 12

Slide 12 text

29 582 Commits There are “only” 15 506 commits for symfony/symfony There are “only” 10 228 commits for joyent/node There are “only” 9 266 commits for twbs/bootstrap There are 44 809 commits for rails/rails (but it’s ruby… #troll)

Slide 13

Slide 13 text

75 contributors There are 1 193 contributors for symfony/symfony

Slide 14

Slide 14 text

20 minutes to deploy the application

Slide 15

Slide 15 text

“Everything should be made as simple as possible but not simpler” Albert Einstein

Slide 16

Slide 16 text

No content

Slide 17

Slide 17 text

➚ Pragmatism “Just get it done, ok?” - God

Slide 18

Slide 18 text

➚ Processes - “Let’s sync!” - “No way man” - A developer and an ops, on a friday evening

Slide 19

Slide 19 text

➚ Learning “It must be somewhere in that file” - A struggling mentor

Slide 20

Slide 20 text

➘ Conflicts “I’ve been rebasing for years, kill me now” - A Git enthusiast

Slide 21

Slide 21 text

➘ Time consuming “The script has been frozen for 30 minutes, should I worry?” - A worried developer

Slide 22

Slide 22 text

➘ Maintenance “It works, but I can’t figure out why” - Both of us

Slide 23

Slide 23 text

➘ Lack of expertise “I’ve only been there for 3 years for God’s sake!” - A senior developer

Slide 24

Slide 24 text

➘ Side effects “The website is broken” - A user on Twitter

Slide 25

Slide 25 text

With minor change comes major bugs.

Slide 26

Slide 26 text

With minor change comes major bugs. Olivier, based on its personal experience.

Slide 27

Slide 27 text

Objectifs BlaBlaCar today.

Slide 28

Slide 28 text

countries NEW IN 2015 India Mexico Hungary Romania Serbia Croatia 19

Slide 29

Slide 29 text

Exponential growth 20 million members in April 2015

Slide 30

Slide 30 text

What are micro- services?

Slide 31

Slide 31 text

Users Ratings Notifications Moderation Trips

Slide 32

Slide 32 text

Objectives - Going worldwide - Fast growing community

Slide 33

Slide 33 text

BlaBlaCar is deploying multiple datacenters.

Slide 34

Slide 34 text

We need to localize our data.

Slide 35

Slide 35 text

Different needs mean different storage.

Slide 36

Slide 36 text

There are only two hard things in Computer Science: cache invalidation and naming things. Phil Carlton

Slide 37

Slide 37 text

The gateway

Slide 38

Slide 38 text

Business Data

Slide 39

Slide 39 text

- How to make it easier for everyone to work together? - How to avoid conflicts? - How to foster expertise?

Slide 40

Slide 40 text

- Micro-startups - Independant teams - Focus on a specific domain - Multi-skills - Limited lifespan Team work

Slide 41

Slide 41 text

No content

Slide 42

Slide 42 text

- Easy to understand - Fast to test, fast to deploy - Framework - Open-source - No more conflicts

Slide 43

Slide 43 text

- Long to bootstrap - Specific projects to handle configuration - Increases ops complexity

Slide 44

Slide 44 text

No content

Slide 45

Slide 45 text

Micro services are not a silver bullet!

Slide 46

Slide 46 text

Migrate from monolithic to micro services can be a pain.

Slide 47

Slide 47 text

t is worth it if you need it!

Slide 48

Slide 48 text

● Micro services are not a silver bullet! ● Migrate from monolithic to micro services is a pain. ● It is worth it if you need it! Benjamin Fraud @bench1ps Olivier Dolbeau @odolbeau