~/talk

Stop Breaking Production - Schema Evolution Demystified

Talkat Scala Days 2026 · 2026-10-12..10-13· [distributed-systems, databases]
links:none on file
slides:none on file

A concrete checklist for avoiding runtime breakage: a product-update Kafka example shows removing categories for tags stops order processing and breaks an ML pipeline, so guarantee consumer-first vs producer-first deployment order and use a schema registry (Confluent) with CI checks against backward/forward/full compatibility. Compare JSON, Avro, Protobuf: use Avro aliases and default enum values, generate code with AvroHugger/ScalaPB, and for Protobuf reserve protobuf field numbers; handle failures with dead-letter topics or stop-consumer semantics and back up the registry DB.

AI-written summary · about

  1. 0:00Introduction and speaker intro
  2. 1:48Problem with schema evolution
  3. 3:12What is schema evolution
  4. 5:18Compatibility types explained
  5. 7:51Serialization formats overview
  6. 11:51Allowed schema changes
  7. 17:09Handling incompatible changes
  8. 18:33Code generation strategies
  9. 21:45Schema registry use
  10. 22:47Recommendations and best practices
  11. 25:17Alternative solutions
  12. 26:23Closing and Q&A
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 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
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
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.