~/talk

Microservice Challenges

Talkat NodeConf EU 2014 · 2014-09-08..09-10· [microservices, nodejs]
slides:none on file

Argues microservices work best when components are tiny, polyglot, and versioned — sometimes three versions running simultaneously — and contrasts synchronous request flows with an event-driven model where every event floods a common pipe. Describes rapids rivers and ponds as an architectural metaphor, warns of exploding message volume (one user can use MQ Series bandwidth up to five percent), recommends separate per-service databases, and notes functional languages like Elixir/Erlang may change how services compose.

AI-written summary · about

  1. 0:00Microservices challenges
  2. 1:45Sync vs async microservices
  3. 3:33Rapids rivers ponds model
  4. 5:57Car rental event demo
  5. 10:48Asynchronous design challenges and benefits
  6. 11:29Microservices vs closure env
  7. 13:54Closure limits in decomposition
  8. 15:19FP and microservices future
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.