Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

You're not Netflix - Ronald van Rijn, CTO, Fuga

28 Aufrufe

Veröffentlicht am

Ronald is CTO at FUGA, the industry-leading technology for international rights holders. He is end-responsible the FUGA platform that was launched in 2008 in conjunction with leading music partners as well as for managing the technical team. Ronald talks about intermittent failures, Netflix from 500 microservices and why you shouldn't consider microservices unless you have a system that is too complex to manage as a monolith. But at the same time don't start a monolith when your goal is a microservices architecture

UXDX Community 2019 - Amsterdam

20th March 2019
Supported by Adyen
Location The Garage, Amsterdam

Video is available to watch on our YouTube channel; https://youtu.be/HOhU1Jr7uC8

Veröffentlicht in: Ingenieurwesen
  • Als Erste(r) kommentieren

  • Gehören Sie zu den Ersten, denen das gefällt!

You're not Netflix - Ronald van Rijn, CTO, Fuga

  1. 1. You’re not Netflix UXDX Amsterdam
  2. 2. Ronald van Rijn
  3. 3. About the title
  4. 4. Once upon a time…
  5. 5. Microservices Premium
  6. 6. Eventual consistency Service A Service B Process 1 Process 2 Write 2 Write 1 Read 1 Read 2 Due to partitioning process 2 might read any of the following: only write 1, only write 2, both or neither
  7. 7. Intermittent failures Service A Service B Process 1 Process 2 Failed write Write Read Read Due to the nature of network traffic any call can fail, at any time and anywhere in the process
  8. 8. “Don’t even consider microservices unless you have a system that is too complex to manage as a monolith.” — Martin Fowler, Thoughtworks
  9. 9. In defence of Monoliths
  10. 10. “Don’t start a monolith when your goal is a microservices architecture.” — Stefan Tilkov, innoQ
  11. 11. Architectures lie on a spectrum
  12. 12. Size of your engineering team
  13. 13. Stage of the product or concept
  14. 14. Domain knowledge of the team
  15. 15. Requirement to deliver part of the system independently
  16. 16. In conclusion
  17. 17. Thank you!

×