BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//sf26-agenda//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
BEGIN:VEVENT
UID:SESS-70@sf26-agenda
DTSTAMP:20261020T151709Z
DTSTART:20261105T193000Z
DTEND:20261105T194500Z
SUMMARY:One Hash\, N Connectors: Parallelizing MongoDB Managed Source Conne
 ctors Without Writing Connector Code
LOCATION:Innovation Theater
DESCRIPTION:Guilherme Ferreira\n\nConfluent Cloud's fully managed MongoDB s
 ource connector is easy to operate; however\, it is limited to one task pe
 r connector. When we needed to move nearly a billion documents (around 20T
 B of data) from MongoDB to Apache Pinot through Kafka each month\, that li
 mit became a serious bottleneck. In this lightning talk\, I'll show how we
  turned one connector into N. Using hash-based filtering in MongoDB's aggr
 egation pipeline\, we assigned multiple managed connectors predictable\, n
 on-overlapping slices of the same collection. No custom connector code\, p
 lugins\, or coordination service required. You'll learn where this pattern
  fits\, how we applied it to both historical backfills and change data cap
 ture\, and the production gotchas we wish we had known about from the star
 t. If a single managed connector is limiting your migration or streaming t
 hroughput\, you'll leave with a practical pattern for scaling horizontally
  while keeping the operational benefits of fully managed infrastructure.
URL:https://sf26.rmoff.net/s/one-hash-n-connectors-parallelizing-mongodb-ma
 naged-source-70
END:VEVENT
END:VCALENDAR