~/talk

Scaling a monolith isn't scaling microservices

Talkat EuRuKo 2018 · 2018-08-24..08-25· [software-architecture]
slides:none on file

Claim: the techniques that scale a large Rails monolith are not the same as those that scale microservices. Describes concrete tradeoffs between Resque and Sidekiq (Ruby task queues), message-oriented middleware / AMQP for service-to-service JSON messages, and Kafka as an event log. Gives numbers: Shopify queues tens of thousands of jobs a second and deploys core code ~60 deploys a day. Shows a working Kafka-powered dashboard that visualises >$1B in Black Friday/Cyber Monday sales.

AI-written summary · about

  1. 0:00Start
  2. 2:29Outline
  3. 9:45Long running jobs - Resque
  4. 10:55Large collections
  5. 11:18Interruptible job with automatic resuming
  6. 13:57Background jobs
  7. 20:01Keep breaking changes manageable
  8. 22:11Event-carried state transfer requires order information
  9. 22:50Event notifications are commutative
  10. 24:55Message oriented middleware
~/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.