Gateway - How to bring down our monolith

Gateway - How to bring down our monolith

Talk given during a PHP meetup in Poland. I present here the main problems of the old BlaBlaCar monolith and how we are trying to change.

0bd054e9a591ec3afb355f5c2c899a23?s=128

Benjamin De Bernardi

October 20, 2015
Tweet

Transcript

  1. 7.

    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)
  2. 10.

    What else ? • Long learning curve • Too many

    side effects • Time consuming • Big maintenance • Spaghetti code
  3. 18.
  4. 19.
  5. 20.
  6. 22.

    • It’s code. • It uses DDD. • Everyone love

    it! • It’s very well organized. • There’s a lot of (very) strict rules. • It separates business logic & data access. • It’s a vendor! It’s easy to use everywhere!
  7. 24.
  8. 25.
  9. 26.
  10. 27.
  11. 28.
  12. 29.
  13. 30.
  14. 31.
  15. 36.

    Gateway • Flexible • Very strict • Easy to test

    • Deployed when needed • Used for all new projects
  16. 38.

    Gateway V3 W W W W W C W C

    C C W Current ecosystem W • 90 workers • 40 commands
  17. 39.

    V3 W W W W W C W C C

    C W Future ecosystem? W Gateway Gateway Gateway
  18. 40.

    V3 W W W W W C W C C

    C W Future ecosystem? W B B B B B B D D D
  19. 41.

    Micro services are not a silver bullet, they won’t solve

    all your problems. We are still working on our gateway stuff :)