Challenges in Implementing Microservices

on YouTube ↗50m

" summary

Argues microservices succeed only with concrete choices: use Kafka (claimed 250,000 messages/sec capacity) and zmq for event rivers, prefer asynchronous event-driven patterns for AB testing and resilience, split monolith databases into many small stores (example team runs 300 microservices), mix languages where appropriate (Ruby/Node/Clojure/Java/Elixir), and instrument KPIs for live testing. Gives a business outcome: a hotel offer engine built for $3M build -> $40M revenue in six months, showing deployment speed and measurable return.

AI-written summary · about

" chapters (6)

1. 0:00Start
2. 7:31Synchronous or Asynchronous
3. 24:48Deconstructing the Databases
4. 28:48MicroServices or Clojure
5. 33:15elixir
6. 33:39Challenge Shitectures and Frameworks

" related talks

• 49mChallenges in Implementing MicroservicesFred George · GOTO Amsterdam 2015
• 48mChallenges in Implementing MicroServicesFred George · Agile Singapore Conference 2016
• 47mIt is not just MicroservicesFred George · GOTO Stockholm 2016
• 16mMicroservice ChallengesFred George · NodeConf EU 2014
• 20m3 reasons why micro-services aren't the miracle cureLisa Mittmann · code.talks 2023
• 23mWhy You Had a Bad Time With MicroservicesEthan Garofolo · EmpireJS 2018
• 43mGo micro with MicroservicesMariusz Gil · International PHP Conference Spring 2017
• 54mThe Long Sad History of MicroservicesGreg Young · Build Stuff 2016