Slicing up a monolithic application Why and how?

Slicing up a monolithic application Why and how?

Talk given with Benjamin Fraud (@bench1ps) at Paris Web 2015

418997665c4a3368515ecf9c3d746b95?s=128

Olivier Dolbeau

October 02, 2015
Tweet

Transcript

  1. 2.
  2. 3.
  3. 4.
  4. 8.
  5. 10.
  6. 12.

    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)
  7. 16.
  8. 18.

    ➚ Processes - “Let’s sync!” - “No way man” -

    A developer and an ops, on a friday evening
  9. 21.

    ➘ Time consuming “The script has been frozen for 30

    minutes, should I worry?” - A worried developer
  10. 23.

    ➘ Lack of expertise “I’ve only been there for 3

    years for God’s sake!” - A senior developer
  11. 36.

    There are only two hard things in Computer Science: cache

    invalidation and naming things. Phil Carlton
  12. 39.

    - How to make it easier for everyone to work

    together? - How to avoid conflicts? - How to foster expertise?
  13. 40.

    - Micro-startups - Independant teams - Focus on a specific

    domain - Multi-skills - Limited lifespan Team work
  14. 41.
  15. 42.

    - Easy to understand - Fast to test, fast to

    deploy - Framework - Open-source - No more conflicts
  16. 44.
  17. 48.

    • 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